From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: libc-alpha@sourceware.org
Subject: use x86_64-linux-gnu compiler
Date: Mon, 03 Jan 2022 07:40:26 +0100 [thread overview]
Message-ID: <mw7dbhe2zp.fsf@tomate.loria.fr> (raw)
Hi,
thanks to the help of H.J., I was able to build a x86_64-linux-gnu compiler
with build-many-glibcs.py.
Now I want to use that compiler to check the accuracy of the recent libmvec
patches. For this I need to link with MPFR, GMP and libmvec. How to proceed?
So far with the following compilation line:
/localdisk/zimmerma/glibc-many/install/compilers/x86_64-linux-gnu/bin/x86_64-glibc-linux-gnu-gcc -I/localdisk/zimmerma/glibc-many/install/host-libraries/include -L/localdisk/zimmerma/glibc-many/install/host-libraries/lib -DWITHOUT_OMP -DLIBMVEC -Ofast -DSTR=$f check_exhaustive.c -mavx2 -lm -lmpfr -lgmp -o /tmp/check_${f}f
I get:
/tmp/check_acosf: /lib/x86_64-linux-gnu/libmvec.so.1: version `GLIBC_2.35' not found (required by /tmp/check_acosf)
/tmp/check_acosf: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /tmp/check_acosf)
When builing glibc there is a testrun.sh wrapper script to use it, is there a
similar wrapper script when using a compiler build from build-many-glibcs.py,
and how to use it?
Best regards,
Paul
next reply other threads:[~2022-01-03 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 6:40 Paul Zimmermann [this message]
2022-01-03 12:50 ` H.J. Lu
2022-01-03 14:29 ` Paul Zimmermann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mw7dbhe2zp.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--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).