From: paul zimmermann <Paul.Zimmermann@inria.fr>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: error when running "make bench"
Date: Thu, 16 Jan 2020 07:57:47 +0100 [thread overview]
Message-ID: <mwzhenkhw4.fsf@tomate.loria.fr> (raw)
In-Reply-To: <CAEMqeSqBv=6Y2Xjz430VM5DcxzbMwzaKRv2=rdumLxNw0TiaQw@mail.gmail.com> (carlos@redhat.com)
Dear Carlos,
> From: "Carlos O'Donell" <carlos@redhat.com>
> Date: Wed, 15 Jan 2020 12:33:01 -0500
>
> On Wed, Jan 15, 2020 at 12:02 PM paul zimmermann
> <Paul.Zimmermann@inria.fr> wrote:
> > with git revision a8f0fc4, when running "make bench" on my machine
>
> What branch has that commit?
it is branch "master":
commit a8f0fc4e5fbad300d524a3339d503c41e3182ed0 (HEAD -> master, origin/master, origin/HEAD)
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Mon Jan 13 20:41:07 2020 +0100
htl: Add internal version of __pthread_mutex_timedlock
The C11 threads implementation will need it.
> > (x86_64 under Linux), I get just before the math tests start:
> >
> > ...
> > /bin/sh: 2: /tmp/glibc/build/benchtests/bench-timing-type: not found
>
> This is a binary that should have been built for you which returns the
> timing type to use.
>
> [carlos@athas glibc]$ /home/carlos/build/glibc/benchtests/bench-timing-type
> hp_timing
>
> > Running /tmp/glibc/build/benchtests/bench-acos
> > Running /tmp/glibc/build/benchtests/bench-acosh
> > ...
> >
> > Is the "not found" message normal?
>
> No. It works just fine for me.
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
Anyway this does not prevent "make bench" to run.
Paul Zimmermann
next prev parent reply other threads:[~2020-01-16 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 16:55 error when running "make bench" paul zimmermann
2020-01-15 17:33 ` Carlos O'Donell
2020-01-16 6:57 ` paul zimmermann [this message]
2020-01-16 9:27 ` Szabolcs Nagy
2020-01-16 10:34 ` paul zimmermann
2020-01-16 16:31 ` Joseph Myers
2020-01-18 12:18 ` paul zimmermann
2020-01-20 11:23 ` Joseph Myers
2020-01-20 11:26 ` Siddhesh Poyarekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mwzhenkhw4.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).