From: Peter Bergner <bergner@linux.ibm.com>
To: Michael Meissner <meissner@linux.ibm.com>,
Thomas Koenig <tkoenig@netcologne.de>,
gcc mailing list <gcc@gcc.gnu.org>,
Bill Schmidt <wschmidt@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [power-ieee128] What should the math functions be annotated with?
Date: Sat, 4 Dec 2021 09:37:20 -0600 [thread overview]
Message-ID: <f5035207-4f1a-cc52-2c77-e920be14f254@linux.ibm.com> (raw)
In-Reply-To: <YauIV6Qz5sH430Cw@toto.the-meissners.org>
On 12/4/21 9:25 AM, Michael Meissner wrote:
> On Sat, Dec 04, 2021 at 02:42:13PM +0100, Thomas Koenig wrote:
> Note, the system ldd does not tend to accurately report the library
> dependencies for AT libraries:
And using AT15's ldd, it shows your a.out is linked to the correct libc:
ubuntu@gcc-fortran:/home/tkoenig/Tst$ ldd ./a.out
./a.out: /lib/powerpc64le-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./a.out)
linux-vdso64.so.1 (0x00007f6339620000)
libc.so.6 => /lib/powerpc64le-linux-gnu/libc.so.6 (0x00007f63393d0000)
/opt/at15.0/lib64/ld64.so.2 => /lib64/ld64.so.2 (0x00007f6339640000)
ubuntu@gcc-fortran:/home/tkoenig/Tst$ /opt/at15.0/bin/ldd ./a.out
linux-vdso64.so.1 (0x00007158fb1c0000)
libc.so.6 => /opt/at15.0/lib64/power9/libc.so.6 (0x00007158faf40000)
/opt/at15.0/lib64/ld64.so.2 (0x00007158fb1e0000)
What I would do is place /opt/at15.0/bin as the 2nd directory in your PATH,
with your new GCC install dir being first. That way, things should be
seemless for you.
Peter
next prev parent reply other threads:[~2021-12-04 15:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 20:34 Thomas Koenig
2021-12-01 20:54 ` Jakub Jelinek
2021-12-01 23:05 ` Jakub Jelinek
2021-12-03 7:29 ` Thomas Koenig
2021-12-03 9:28 ` Jakub Jelinek
2021-12-03 11:16 ` Thomas Koenig
2021-12-03 11:35 ` Jakub Jelinek
2021-12-03 11:56 ` Thomas Koenig
2021-12-03 14:57 ` Bill Schmidt
2021-12-04 6:39 ` Michael Meissner
2021-12-04 9:33 ` Thomas Koenig
2021-12-04 10:16 ` Thomas Koenig
2021-12-04 10:29 ` Jakub Jelinek
2021-12-04 13:42 ` Thomas Koenig
2021-12-04 15:25 ` Michael Meissner
2021-12-04 15:37 ` Peter Bergner [this message]
2021-12-04 16:12 ` Peter Bergner
2021-12-04 16:19 ` Jakub Jelinek
2021-12-04 22:27 ` Peter Bergner
2021-12-04 17:40 ` Thomas Koenig
2021-12-05 0:35 ` Peter Bergner
2021-12-05 11:16 ` Thomas Koenig
2021-12-06 22:31 ` Michael Meissner
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=f5035207-4f1a-cc52-2c77-e920be14f254@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=tkoenig@netcologne.de \
--cc=wschmidt@linux.ibm.com \
/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).