This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: testing glibc
- From: Carlos O'Donell <carlos_odonell at mentor dot com>
- To: Andi Kleen <andi at firstfloor dot org>
- Cc: <libc-alpha at sourceware dot org>
- Date: Fri, 22 Jun 2012 16:34:43 -0400
- Subject: Re: testing glibc
- References: <20120622202547.GQ11413@one.firstfloor.org>
On 6/22/2012 4:25 PM, Andi Kleen wrote:
>
> When I want to test an experimental glibc and do not want to mess up
> my system I always did it like this
>
> cd obj
> ../glibc/configure --prefix=/some/dir
> make
> sudo make install
>
> LD_LIBRARY_PATH=/some/dir program
> sometimes when the program uses dlopen and crashes do
> LD_LIBRARY_PATH=/some/dir /some/dir/lib/ld-linux-x86-64.so.2 program
> (or relink program)
>
> However on recent git glibcs this doesn't work anymore. With a FC16 host
> I always get
>
> ls: error while loading shared libraries: __vdso_gettimeofday: invalid
> mode for dlopen(): Invalid argument
>
> When I run it with the new ld-linux.so it seems to be unable to read the
> system shared library path, so nothing works.
>
> What's the currently recommended way to test glibc without replacing the
> system libc?
Does installing an appropriate ld.so.conf into /some/dir/etc/ help?
We have been doing more to make the install relocatable, and thus
isolated from the system root, and this means your alternate root
needs to be slightly more complete.
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026