fixincludes problem
Andrew Crabtree
andrewc@typhoon.rose.hp.com
Mon Jan 12 20:31:00 GMT 1998
> > > Set FIXINCLUDES to "Makefile.in" in the Makefile.
> > Thank you. I ran across this for other configurations but
> > wasn't sure if it was what I should do or not.
> Which ones? There should be _very_ few which do this.
alpha*-*-linux-gnuecoff*)
alpha*-*-linux-gnulibc1*)
alpha*-*-linux-gnu*)
alpha*-dec-vms*)
arm-semi-aout | armel-semi-aout)
arm-semi-aof | armel-semi-aof)
arm-*-linux-gnuaout*)
c1-convex-*)
c2-convex-*)
c32-convex-*)
c34-convex-*)
c38-convex-*)
hppa1.1-*-osf*)
hppa1.0-*-osf*)
hppa1.1-*-bsd*)
hppa1.0-*-bsd*)
hppa*-*-lites*)
i[3456]86-*-linux-gnuoldld*)
i[3456]86-*-linux-gnuaout*)
i[3456]86-*-linux-gnulibc1)
i[3456]86-*-linux-gnu*)
i[3456]86-moss-msdos* | i[3456]86-*-moss*)
i[3456]86-*-pe | i[3456]86-*-cygwin32)
i[3456]86-*-mingw32)
OK - I'm getting tired of copying and pasting. :) None of these
seem too mainstream though...
> Most include files have subtle bugs in them, regardless of where they
> originate from. It has nothing to do with native vs cross -- whatever
> include files you're using need to be scanned and problems fixed.
OK - But for DJGPP the header files are designed to work only
with GCC. There is no native system that they were coded for.
Since cygwin disables fixincludes is it reasonable to
do for DJGPP also?
> An interesting exercise might be to run fixincludes and see exactly what
> it changes for the include files for djgpp.
Well, this is how i found it it was a problem originally of course.
Stdio and stddef had fatal errors in both for starters. I
am in the middle of bootstrapping so scrapped the bad headers but
will repeat when I'm done.
Andy
--
_______ ___________________________________________________________
/ Andrew Crabtree
/ Workgroup Networks Division
____ ___ / Hewlett-Packard
/ / / / Roseville, CA
__/ __/ _____/ 916/785-1675
/ andrewc@rosemail.rose.hp.com
___________ __/ _____________________________________________________
More information about the Gcc
mailing list