This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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]

Re: which glibc to use

From: Ian Lance Taylor <iant at google dot com>
To: "Koornstra\, Reinoud" <koornstra at hp dot com>
Cc: "gcc-help\ at gcc dot gnu dot org" <gcc-help at gcc dot gnu dot org>
Date: Wed, 11 Mar 2009 07:03:09 -0700
Subject: Re: which glibc to use
References: <E92FAF79A8BBC642A36EEE3AA7F152D8341C6F5595@GVW1089EXB.americas.hpqcorp.net> <m3tz669jvp.fsf@google.com> <E92FAF79A8BBC642A36EEE3AA7F152D83CF384C322@GVW1089EXB.americas.hpqcorp.net> <m3sklm3p5x.fsf@google.com> <E92FAF79A8BBC642A36EEE3AA7F152D83CF384C95B@GVW1089EXB.americas.hpqcorp.net>

"Koornstra, Reinoud" <koornstra@hp.com> writes:

> Any other things I need to have before being able to successfully build glibc?

I don't routinely build glibc, so I don't know.  Note that building a
new glibc to replace your system glibc is a job for experts; there are
many subtle issues.  Building a new glibc for a new system is something
handled well by crosstool (http://kegel.com/crosstool).

Ian

Follow-Ups:
- RE: which glibc to use
  - From: Koornstra, Reinoud

References:
- libstdc issue
  - From: Koornstra, Reinoud
- Re: libstdc issue
  - From: Ian Lance Taylor
- which glibc to use
  - From: Koornstra, Reinoud
- Re: which glibc to use
  - From: Ian Lance Taylor
- RE: which glibc to use
  - From: Koornstra, Reinoud

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]