This is the mail archive of the
mailing list for the glibc project.
Re: pthread_cond_* does not compile on i386
- From: "Bert Wesarg" <bert dot wesarg at googlemail dot com>
- To: "Ryan Arnold" <ryan dot arnold at gmail dot com>
- Cc: "Carlos O'Donell" <carlos at systemhalted dot org>, "Gilles Carry" <Gilles dot Carry at bull dot net>, libc-help at sourceware dot org
- Date: Sat, 3 May 2008 12:21:34 +0200
- Subject: Re: pthread_cond_* does not compile on i386
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.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=EzI0toTnVjNgQ4Z32XnceQtDzaKp5JONLSs/EpN1xY4=; b=aguTrQuPGsNXOiF6mgAKtqLm3o1FVmfdj27GxDYaR4d8bFtCXxCHwcLuiueGG0aANDWImfW4APoo84p/pz6u8OyFwLHNX76lYR8TKv8OTGcCP8rY4ba31e0JgsRbpMAoUPnEyU9TjTY3ZctNSUd+iiEOKmVOKV+cdNB0pS6770I=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.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=ERJAiTZI0LvG3uT/IdaFVuLOJSlueHmld4zIQ/pNRg3du3TbNR0pkipIp6ZKEcG1OEFXLKwMuE94y5viQlxN/qZ4MvfDFWuLhF0f67iJPwTignVdPLWq3PJQjhzswfzawN1c/aAvwieicOUrxtm7wBwjyfjU37ZZnL+VlIGRiN8=
- References: <48185CA9.email@example.com> <firstname.lastname@example.org> <email@example.com>
On Sat, May 3, 2008 at 3:58 AM, Ryan Arnold <firstname.lastname@example.org> wrote:
> On Fri, May 2, 2008 at 8:25 AM, Carlos O'Donell <email@example.com> wrote:
> > On Wed, Apr 30, 2008 at 7:48 AM, Gilles Carry <Gilles.Carry@bull.net> wrote:
> > > By the way, is there any official way or document that explains how to
> > > build glibc? ... just to be sure I'm not missing something.
> > The standard configure, make, make -k check is good enough to build
> > the library. However, make install has to be used with care, and it
> > does involve pivoting a root, and rebooting to actually fully use the
> > new glibc.
> Hrm, I have three methods for testing a glibc build documented. I
> should probably push that document to the wiki.
> 1.) install into a chroot, test, copy over system library.
> 2.) invoke new loader to invoke new libc.
> 3.) build and install a self contained toolchain.
Yes, please. I tried this several times in the past years and always
failed. One question: have you also got a multilib version running, ie
x86-32 and x86-64?
Thanks in advance.
> Ryan S. Arnold