This is the mail archive of the
mailing list for the glibc project.
Re: Building glibc from CVS on x86 Ubuntu Hardy
- From: "Ryan Arnold" <ryan dot arnold at gmail dot com>
- To: "Reuben Thomas" <rrt at sc3d dot org>
- Cc: "Ryan S. Arnold" <rsa at us dot ibm dot com>, libc-help at sourceware dot org
- Date: Sat, 3 May 2008 08:51:01 -0500
- Subject: Re: Building glibc from CVS on x86 Ubuntu Hardy
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=B4KTwpfacocwIanxqElSvpErQY0BMzpYFnSr1sSeQ+s=; b=cxpB+zH1d+PIGh9kouVX59g/o5qAHTx+D511+vKJM6jGYjEQOHOqf99FG63C9c6QdG+2k9UPeuYANk9UCzjdmjPG3CNelLm0gJMMmC8Hkw9ZzqU9XsdPQKPYLtSwSD/5FltU0tzGt191tr04yRbv4J61N95j5xmQjKB4WQkCQgs=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tcH4j+AbkJd94MiW92KlFlMdbEj7wGdygW88YzNwrAj+JBBki8Id84WfAiB0zlqTtXTGYPMhiScLik0fn+OkG+8g08QERPzjYRM8VPIyj7ShlhodQTgb1SAachntO2snzdnSTcAir2icMFWQ/fi1AUQlQaamsyNo0Q5glzKNdUY=
- References: <alpine.DEB.1.00.0805022336320.10349@canta> <1209774805.11694.4.camel@localhost> <alpine.DEB.1.00.0805031211310.10349@canta>
On Sat, May 3, 2008 at 6:44 AM, Reuben Thomas <email@example.com> wrote:
> On Fri, 2 May 2008, Ryan S. Arnold wrote:
> Thanks, that works fine. Where should I have discovered that this is what I
> needed to do? As far as I could tell from INSTALL, I should have been able
> to use the simple line that I used. Or is this a problem with building on
In general the developers don't like to encourage the
building/installing of GLIBC. Every build of glibc is specially tuned
for the target therefore a simple bare 'configure' isn't appropriate.
> > Try it without the -fno-stack-protector too to see if that works.
> That doesn't work. Why not? I see it says "Checking for -fstack-protector"
> while configuring. Is it because the Ubuntu compiler switches this on by
> default and the libc configure doesn't know to turn it off?
-fno-stack-protector used to be required on my Ubuntu machine. This
may not be the case any longer with a newer compiler.