This is the mail archive of the
mailing list for the glibc project.
Re: Error building glibc-2.10.1
- From: "Justin P. Mattock" <justinmattock at gmail dot com>
- To: JohnT <jrt at worldlinc dot net>
- Cc: libc-help <libc-help at sourceware dot org>
- Date: Wed, 18 Nov 2009 10:24:24 -0800
- Subject: Re: Error building glibc-2.10.1
- References: <4B03A4D2.firstname.lastname@example.org> <4B03A76B.email@example.com> <4B03E7B5.firstname.lastname@example.org>
Justin P. Mattock wrote:
If so, then the configure script missed some things, maybe version
numbers of system source libs needed to build the libc-pic.os library
Since the current or previous release of Centos (Redhat Enterprise)
used glibc-2.5x, I thought it would be considered recent, but here's
a glibc-2.10.1 problem I encountered. The configuration settings were:
--prefix=/usr CFLAGS=" -O2 -march=i686"
/home2/on07/bldlib210/libc_pic.os: In function `fallocate':
(.text+0xaedb4): undefined reference to `__call_fallocate'
/home2/on07/bldlib210/libc_pic.os: In function `__fallocate64_l64':
(.text+0xaedc5): undefined reference to `__call_fallocate'
collect2: ld returned 1 exit status
make: *** [/home2/on07/bldlib210/libc.so] Error 1
make: Leaving directory `/home2/on07/glibc-2.10.1'
make: *** [all] Error 2
Again, help in resolving this so I can get a successful build would
be appreciated. The assembler syntax change was a very good tip, not
obvious from binutils or gas changelog.
not sure whats happening, but by
just glancing I see that:
libc_pic.os was/is being built
with no idea about __call_fallocate'
maybe a header file, or a library
that's been built with the wrong dependencies.
Justin P. Mattock
http://www.mozilla.org Firefox browser, Thunderbird email, Seamonkey all-in-one, Sunbird calendar and more. Free open-source software for Windows, Linux, Mac OS and other systems
could be, but if you compiled another program/lib the wrong
way then glibc's configure script wouldn't know the
Justin P. Mattock