getting glibc from cvs

Michael Kerrisk
Wed Jul 30 13:33:00 GMT 2008

Ryan Arnold wrote:
> On Tue, Jul 29, 2008 at 5:27 AM, Oussama Chammam <> wrote:
>> I am trying to build glibc-2.7 but it fails to make, I am building it with the glibc-libidn-2.7 addon.
>> wehen I type "make" I got following error at the end:
> Oussama,
> Why don't you use glibc 2.8 instead.  GLIBC 2.7 is the last tar
> created but Ulrich and company have stopped creating tar releases,
> relying instead on CVS branches for new releases.  The latest is 2.8
> and you can get it with the following:
> cvs -z 9 -d login
> {enter "anoncvs" as the password}
> cvs -z 9 -d co -r
> glibc-2_8 -P libc
>> /media/sda1/usr/src/glibc-build/libc_pic.a(init-first.os):(.data+0x0): multiple definition of `__libc_multiple_libcs'
>> /media/sda1/usr/src/glibc-build/elf/dl-allobjs.os:/media/sda1/usr/src/glibc-2.7/elf/rtld.c:644: first defined here
>> /media/sda1/usr/src/glibc-build/libc_pic.a(dl-addr.os): In function `_dl_addr_inside_object':
>> /media/sda1/usr/src/glibc-2.7/elf/dl-addr.c:157: multiple definition of `_dl_addr_inside_object'
>> /media/sda1/usr/src/glibc-build/elf/dl-allobjs.os:/media/sda1/usr/src/glibc-2.7/elf/dl-open.c:699: first defined here
> I think something is wrong with your configure fragment.
>> when I type "make test", I got the following error:
> There is no 'make test'.
>> when I type "make check", I got the following error:
> If 'make' didn't pass then 'make check' surely won't pass.
>> I configured glibc by typing:
>>  ../glibc-2.7/configure --enable-add-ons --prefix=/usr
>> and have even tried:
>> ../glibc-2.7/configure --disable-stackguard-randomization --enable-old-ssp-compat --enable-omitfp --enable-add-ons=nptl --enable-kernel=linux-2.6.26 --without-selinux --without-cvs --enable-bind-now --build=x86_64-linux-gnu --host=x86_64-linux-gnu --disable-profile --with-gd --with-headers=/media/sda1/usr/src/linux-2.6.26/include --prefix=/usr --libdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --libexecdir=/usr/lib/misc/glibc
> This doesn't look sufficient.  I believe you'll need some indication
> of -march for x86_64.  --enable-add-ons as a bare switch doesn't work
> either (it'll complain about 'crypt').  You'll want to use
> --enable-add-ons=nptl.  If libidn is really an 'addon' then you'll
> need: --enable-add-ons=nptl,libidn
>> or may that has something with the glibc-libidn-2.7 addon??
> Where'd you get this libidn add-on?
> Perhaps someone with some knowledge of building for x86_64 can help
> out with a valid configure fragment.
> Regards,
> Ryan S. Arnold

More information about the Libc-help mailing list