This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: error when running "make bench"
thank you Szabolcs, this solved the problem.
However, I believe the issue is on the glibc side. Indeed, the
bench-timing-type is linked with /tmp/lib/ld-linux-x86-64.so.2
by the glibc Makefile, and that file doesn't exist if "make install"
was not done (I configured with ./configure --prefix=/tmp).
Thus either benchtests/README should indicate that "make install" should
be done, or the compile line for bench-timing-type should not link with
files in $PREFIX.
To reproduce:
$ git clone git://sourceware.org/git/glibc.git
$ cd glibc
$ mkdir build
$ cd build
$ ../configure --prefix=/tmp
$ make -j4
$ make bench
Best regards,
Paul
> From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
> CC: nd <nd@arm.com>, "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
> Thread-Topic: error when running "make bench"
> Thread-Index: AQHVy8STAjP+xHdPFUeTg1WXkdE96Kfr/CKAgADg6e+AACnCAA==
> Date: Thu, 16 Jan 2020 09:27:36 +0000
> user-agent: Mozilla/5.0 (X11; Linux aarch64; rv:60.0) Gecko/20100101
> Thunderbird/60.9.0
> nodisclaimer: True
> Original-Authentication-Results: spf=none (sender IP is )
> smtp.mailfrom=Szabolcs.Nagy@arm.com;
>
> On 16/01/2020 06:57, paul zimmermann wrote:
> > what is strange is that the file exists:
> >
> > $ ls -l /tmp/glibc/build/benchtests/bench-timing-type
> > -rwxr-xr-x 1 zimmerma caramba 35760 Jan 16 07:48 /tmp/glibc/build/benchtests/bench-timing-type
> >
> > $ file /tmp/glibc/build/benchtests/bench-timing-type
> > /tmp/glibc/build/benchtests/bench-timing-type: ELF 64-bit LSB shared object,
> > x86-64, version 1 (SYSV), dynamically linked, interpreter /tmp/lib/ld-linux-x86-64.so.2,
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > BuildID[sha1]=6eaee68beda7ba9d3a4e7c329d427b5c0676483d, for GNU/Linux 3.2.0, with debug_info, not stripped
> >
> > however it does not want to run:
> >
> > $ /tmp/glibc/build/benchtests/bench-timing-type
> > -bash: /tmp/glibc/build/benchtests/bench-timing-type: No such file or directory
>
> that executable seems to be built with
>
> -Wl,-dynamic-linker=/tmp/lib/ld-linux-x86-64.so.2
>
> which does not exist, you can quickly fix it now
> by making that a symlink to wherever the dynamic
> linker is (and set up runtime library paths where
> libc.so.6 etc is)
>
> but i think ideally your host toolchain should
> not produce executables that cannot run.