This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, Jan 07, 2004 at 08:06:15PM -0500, Raul Miller wrote:
On Wed, Jan 07, 2004 at 04:38:05PM -0800, Daniel Kegel wrote:
BTW, why do you build glibc twice?
I thought it was important at one point, but I forget why.
It's needed when bootstrapping glibc, ie. if you don't have a previous libc and crt* files available. The trouble is that building a shared glibc requires crt* to build, and the glibc build machinery isn't clever enough to pick up newly built crt* files. Also, gcc's configure makes use of AC_TRY_LINK, which again needs crt files. :-(
I haven't run into those problems, I think. In http://kegel.com/crosstool, I do * install glibc headers * build bootstrap gcc * build and install glibc * build and install final gcc and I happily get a shared glibc that passes the glibc regression tests.
I seem to recall that one reason people used to build glibc twice was to get the paths right, but that's not really neccessary if you override install_root when doing 'make install' in glibc.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |