Re: Sockets

[Simon Wright <simon@pushface.org>]

dewar@gnat.com (Robert Dewar) writes:

> Simon Wright <simon@pushface.org> wrote in message news:<x7v8z68fyd7.fsf@pushface.org>...
> 
> > It was quite simple to get GNAT.Sockets working on VxWorks (NB, if you
> > are using 3.14p with VxWorks I think you may find that GNAT.Sockets
> > assumes Linux conventions for various constants, which are different
> > from VxWorks -- and for once Linux is out on a limb. I have a patch,
> > originally for 3.14a1, mail me at simon.j.wright@amsjv.com)
> 
> No, GNAT.Sockets does not assume Linux conventions. There are different
> target dependent versions for various targets, including a VxWorks
> specific set of units. We don't make judgments as to who is out on
> a limb, but for sure there are differences and the current version
> of GNAT.Sockets in GNAT Pro is implemented for all native targets
> except OpenVMS, and all cross targets except Lynx (those two
> will be filled in sometime in the near future).

I did say 3.14{p,a1}! There was no official support for GNAT.sockets
on VxWorks in 3.14a1 though the source was in the RTL, and (for the NT
cross PPC 3.14a1) the version of GNAT.Sockets etc in the library was
the Linux one, I'm pretty sure. And GNAT.Sockets.Constants had Linux
constants in it. But it wasn't too hard to figure out, and we got it
working with a day or so's effort.

Of course anyone who wants to build a 3.14p/VxWorks cross is going to
have fun. Might be more productive to try with GCC 3.1.