This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
RE: stdio&unistd for cross compilation
- To: don at pixsci dot com
- Subject: RE: stdio&unistd for cross compilation
- From: mrs at wrs dot com (Mike Stump)
- Date: Tue, 21 Apr 1998 14:04:19 -0700
- Cc: egcs-bugs at cygnus dot com
> From: Don Bowman <don@pixsci.com>
> Date: Mon, 20 Apr 1998 23:39:06 -0400
> Does cygnus configure the GNUPro toolkit for each and every target
> system?
Yes.
> Does this mean there is a version of this for VxWorks, one for
> RTEMS, one for Lynx, etc?
Yes.
> Does this mean you have to have each of these OS's build environment
> installed to build the toolkit?
Yes.
> What if the header files are incompatible between the releases of
> the OS?
Then they (we) fix it.
> As an example... the VxWorks header files are not useful unless
> -DCPU=...
This is done automatically for the user in some cases. In other
cases, we just haven't fixed it yet.
> -DRW_MULTI_THREAD
This one isn't necessary for the compilers libraries.
> -D_REENTRANT
If this is a problem, we can handle it as we do CPU.
> -D<some endianness flag specific to CPU> -D__VXWORKS__ are
> defined.
Ditto.
> configure doesn't know about this.
It already knows about some of them, though, maybe not all.
> I'm not that interested in adding it. Until fairly recently these
> header's weren't even ansi.
I'll try and work that problem from this end.