On Sunday 31 January 2010 12:32:21, Dave Korn wrote:
> I don't think it should be necessary to patch the build system, since it's
> already capable of doing the right thing (which is to create the private
> header and fixed syslimits), we need to understand why it isn't doing that.
>
My guess is that with the options we're building gcc,
gcc isn't looking at ($tooldir)/includes for fixincludable headers, but
at ($tooldir)/sys-includes. So it just installs its own limits.h as if
the system doesn't have one already.
I think we should be building gcc with `--with-sysroot=${PREFIX}/arm-mingw32ce/'
Might work to pass --with-headers=($tooldir)/includes to gcc too, but that
feels hackish.
Oh, and the bootstrap gcc's headers get installed at the same
place as the final gcc. If the bootstrap gcc installs headers
the final gcc doesn't, we end up with stale headers installed.
We should be installing the bootstrap compiler in a staged
dir (or better, everything)..
--
Pedro Alves
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
