This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: pthread_cond_* does not compile on i386
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Gilles Carry" <Gilles dot Carry at bull dot net>
- Cc: libc-help at sourceware dot org
- Date: Fri, 2 May 2008 09:25:20 -0400
- Subject: Re: pthread_cond_* does not compile on i386
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=5SsWXEeaK223O0/wm7IHWa9Z889HV0Lw8sUsfEhOkFs=; b=RqTZ5XgqiK3aqOe3V3X2pwQf3mJlp8mC4TVHsIKFPLu7a6u+9q/nDYmfDYCeYY2bcDhrh/8zMv6OyPZmjMzW1bsL0YMyuIx5w5UNsnOEvzT+DUFwzq79HKVVghMQpJOjuQFNmnqYYxivd+WM1RKrr7Rz143gUYlTcrAe1m7M6L0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=JnJs4ye2O/eA1a8BYvzpRXjOoKof6rdkc2h0h7XFs2vuueX8torOkwh+KZ9gnhQc/QbxsaTQayZxBUeD4UHPthkPn4gFw5LWgt7sb7pjrvHg445m0hrOEK0s3TfdGxz1isL3U5LpaeLJ9pS/5BthVCQbgMGp90I34M0T7fWEzIw=
- References: <48185CA9.8010607@bull.net>
On Wed, Apr 30, 2008 at 7:48 AM, Gilles Carry <Gilles.Carry@bull.net> wrote:
> After having removed the corresponding asm files, pthread_cond_signal.c
> fails compiling.
Why would you remove the asm files that implement the required behaviour?
> Actually, pthread_cond_signal.c uses the macro lll_futex_wake_unlock
> which is not defined for i386.
> At least I cannot find it by grepping through the source tree.
> To have it compiling, I had to rework the syscall macros.
>
> Though I can build the rest of glibc without error, I wonder if the C code
> and asm-i386 are in sync for pthread_cond_* files.
They don't need to be kept "in sync", the i386 port probably doesn't
rely on the C code variants of these functions.
> 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.
Cheers,
Carlos.