emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#9396: closed (make fails with undefined reference


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#9396: closed (make fails with undefined reference to '__sched_cpucount')
Date: Tue, 13 Sep 2011 09:49:02 +0000

Your message dated Tue, 13 Sep 2011 11:43:52 +0200
with message-id <address@hidden>
and subject line Re: bug#9396: make fails with undefined reference to 
'__sched_cpucount'
has caused the debbugs.gnu.org bug report #9396,
regarding make fails with undefined reference to '__sched_cpucount'
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
9396: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9396
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: make fails with undefined reference to '__sched_cpucount' Date: Sun, 28 Aug 2011 21:59:56 +0000

Howdy,

 

I’m trying to compile coreutils-8.12 in a Dell Xeon workstation environment that runs Redhat 5 (RHEL5). After some time, make fails with:

 

+verbatim+

../lib/libcoreutils.a(nproc.o): In function `num_processors_via_affinity_mask':

/home/afbacher/GCC/coreutils-8.12/lib/nproc.c:137: undefined reference to `__sched_cpucount'

collect2: ld returned 1 exit status

make[3]: *** [nproc] Error 1

make[3]: Leaving directory `/home/afbacher/GCC/coreutils-8.12/src'

make[2]: *** [all] Error 2

make[2]: Leaving directory `/home/afbacher/GCC/coreutils-8.12/src'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/home/afbacher/GCC/coreutils-8.12'

make: *** [all] Error 2

-verbatim-

 

I tracked the problem down to the fact that the RHEL5 system uses /lib64/libc.so.6 which apparently is version 2.5 of the GNU C Library, but this version does not contain “__sched_cpucount” – whatever that is. Apparently only version 2.6 and later contain this stuff.

 

One problem is that I’m not the sysadmin for this system, and I don’t think this can be updated without breaking a lot of other stuff. How do I get around this? I’m only trying to compile a bunch of programs for my own use, not for the entire system.

 

I’m actually trying to compile glibc-2.14 for various reasons, along with a bunch of other basic GNU software (like gcc-4.6.), and I found that when glibc’s installer installs various coreutils programs like rm, as soon as these get installed the programs quit working because of incompatible ABI’s and such. That’s why I thought I needed to install the latest coreutils.

 

I’m probably missing something badly, but I more than a bit confused about the order in which the various sets of software need to be installed in order to keep it all consistent.

 

One thing I’ve done is to make my $PATH contain the path to my newly built programs. That’s why, when the glibc installer installs rm and such, various other programs quit working, because there’s a lot of interdependence. So what’s my best approach with all this?

 

Alan Feuerbacher


--- End Message ---
--- Begin Message --- Subject: Re: bug#9396: make fails with undefined reference to '__sched_cpucount' Date: Tue, 13 Sep 2011 11:43:52 +0200
tags 9396 notabug
thanks

Paul Eggert wrote:
> On 08/28/11 14:59, Feuerbacher, Alan wrote:
>> I tracked the problem down to the fact that the RHEL5 system uses
>> /lib64/libc.so.6
>> which apparently is version 2.5 of the GNU C Library,
>> but this version does not contain "__sched_cpucount" - whatever that is.
>> Apparently only version 2.6 and later contain this stuff.
>
> It sounds like you're compiling with glibc 2.6 headers but linking
> to glibc 2.5.  If so, that'd be a definite no-no; you need to configure
> and build with <= 2.5 headers if you're going to link with 2.5.
>
> I expect that it's the 2.6 headers that #define CPU_COUNT and bring
> in a reference to __sched_cpucount.

Thanks for the report.
Since we haven't heard back from you, I presume that
Paul's diagnosis was correct and have thus closed this bug.
If not, please let us know.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]