Building a cross compiler, and unsure about the use of --without-headers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I'm currently building a cross compiler and tool chain for an embedded
Sparc system project, and have most of it working OK.  However,
checking over my configuration and building steps I'm a little
confused about the use of "--without-headers", and wondered if anyone
could shed some light on what it does, and when I should be using it.

Based on various examples of building cross systems around the net, I
have a procedure where the compiler gets built twice, once as a basic
version to allow building of Newlib, and then again as the full cross
compiler version.  Looking at the esamples, the first, basic, build
always seems to use --without-headers (and --with-newlib).  For the
second build however, some sites have both of these again, while
others have only --with-newlib, so I'm not sure whether I should
include this option in my second stage build or not...

A search turns up a few references to this option, but none of them
say much beyond something along the lines of "leaving it out will
disable some features".  Does anybody have any thoughts on the wisdom
or otherwise of using this option?

(This may be a question more suited to the cross-gcc list, and if so
I'll repost it there.)

Regards,

David P.


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux