From: Florian Weimer <fweimer@redhat.com>
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: libc-alpha@sourceware.org
Subject: Re: test old versions of glibc
Date: Mon, 07 Mar 2022 13:53:42 +0100 [thread overview]
Message-ID: <87r17dc4a1.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <mwtuca55cx.fsf@tomate.loria.fr> (Paul Zimmermann's message of "Mon, 07 Mar 2022 13:12:14 +0100")
* Paul Zimmermann:
> Hi,
>
> I have an application that I want to test with old versions of glibc.
> The following usually works:
>
> $ gcc -fno-builtin test_pow.c -lm
> $ /localdisk/zimmerma/glibc-2.29/build/testrun.sh ./a.out
> z=0x1.fffeb4d85aa15p-1010
>
> However with glibc-2.28 it fails, because the binary contains a call to
> pow@GLIBC_2.29:
>
> $ nm a.out | grep pow
> U pow@GLIBC_2.29
>
> $ /localdisk/zimmerma/glibc-2.28/build/testrun.sh ./a.out
> ./a.out: /localdisk/zimmerma/glibc-2.28/build/math/libm.so.6: version `GLIBC_2.29' not found (required by ./a.out)
>
> How can I disable the check for GLIBC_2.29 (this is for my particular
> application, and I know what I'm doing)?
As a quick hack, adding
asm (".symver pow, pow@GLIBC_2.2.5");
will work.
We should probably put gcc and g++ wrappers in the build tree alongside
with testrun.sh, to simplify building against the uninstalled glibc.
Thanks,
Florian
next prev parent reply other threads:[~2022-03-07 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 12:12 Paul Zimmermann
2022-03-07 12:53 ` Florian Weimer [this message]
2022-03-08 10:09 ` 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=87r17dc4a1.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=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).