This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
fixincludes takes wrong files? (possible sysroot/build-sysroot confusion?)
- From: Jay <jayk123 at hotmail dot com>
- To: <gcc at gcc dot gnu dot org>
- Date: Thu, 24 Jul 2008 10:09:23 +0000
- Subject: fixincludes takes wrong files? (possible sysroot/build-sysroot confusion?)
starting from build i686-pc-cygwin
build native
build host i686-pc-cygwin target sparc-sun-solaris2.10 -with-sysroot
and then host sparc-sun-solaris2.10 target sparc-sun-solaris2.10
installing with destdir = /usr/local/sparc-sun-solaris2.10/install
fixincludes took
d:\cygwin\usr\include\math.h
instead of:
D:\cygwin\usr\local\sparc-sun-solaris2.10\sys-root\usr\include\math.h
and produced:
D:\cygwin\usr\local\sparc-sun-solaris2.10\install\usr\local\lib\gcc\sparc-sun-solaris2.10\4.3.1\include-fixed\math.h
which didn't work, of course (for a simple reason -- _PARAMS via _ansi.h vs. __P locally)
Perhaps the third toolset should be built -with-sysroot=/ -with-build-sysroot=/usr/local/sparc-sun-solaris2.10/sys-root?
Anyway, I renamed the include-fixed away and am rebuilding native.
I'll have to dig around and plan to start over "from scratch" anyway and see.
I realize these incorrect headers, or what all they are a sign of, *might* have "infected" the tools.
The -sysroot stuff is still confusing me some.
The other day I found it useful to symlink /usr/local//sys-root to / in order to "fake something out".
The -build-sysroot doc says it is only useful with -sysroot, but it seems to me that may be false.
I wish sysroot could be validated early, in configure, and user new to cross/etc. builds given a little more hand holding, oh well.
- Jay