Re: LynxOS 3.1.1 Port

[Joel Sherrill]

Pierre Bacquet wrote:
> 
> Joel,
> 
> > I am entering the test phase of my port of Common C++ to LynxOS
> > 3.1.1.  I am filing the appropriate paperwork with the FSF but
> > for now want to get some feedback on some porting issues and
> > how to do them more cleanly.  Right now, there are a handful
> > of __Lynx__ conditionals I want to eliminate.
> >
> > (2) inet_aton(char *, .. )     not inet_aton(const char *, ..)
> >     gethostbyname(char *, .. ) not gethostbyname(const char *, ..)
> >     openlog(char *,..)         not openlog(const char *, ..)
> >
> > Again how to detect and deal with this without stopping to
> > ifdef __Lynx__.
> 
> Well, taking into account the fact that these 3 functions shouldn't
> change their "char *" arg., hence the const keyword, one possible
> action would be to patch the LynxOS headers to change the signature
> and send the patched files to LynxOS maintainers for possible
> consideration.

That occurred to me as well.  But there is already a major update to
LynxOS which transitions to ELF (4.0.0) and it has inet_aton() and
gethostbyname() with const but openlog() still doesn't have a const.
So that isn't going to get fixed in the near future.  

If I added a README.LynxOS with specific instructions on fixing the 
LynxOS 3.1.1 and 4.0.0 header files, would that help?  

But at least fixing the 3.1.1 header files by hand would eliminate
most of the hacks for both versions.  openlog() is used only once.

Thanks for making me doublecheck my thoughts.  I don't want to
ugly things up. :)

> Cheers,
> 
> Pierre.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
address@hidden                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985