From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Evan Cooch <evan.cooch@gmail.com>
Cc: Jim Wilson <jimw@sifive.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: gfortran | 9.3.1 missing FINDLOC?
Date: Tue, 30 Mar 2021 16:22:49 +0100 [thread overview]
Message-ID: <CAH6eHdS+vPeGktBNZgwaYea_JmeO6MOf52=bjkt=S+QzsRySdA@mail.gmail.com> (raw)
In-Reply-To: <04c62634-a957-db31-1714-fc40c1fb5ca8@gmail.com>
On Tue, 30 Mar 2021 at 16:14, Evan Cooch wrote:
> Many thanks. That gave me a clue. Turns out that if I statically link
> libgfortran (-static-libgfortran), findloc is found (unavoidable irony).
> But, if I use a dynamic link, it is not staying with the scl env, and is
> using the libgfortran that CentOS 7 (and RHEL 7) defaults to, which is
> << gcc 9. Which, if I'd stoped to think about it, sort of makes sense.
If you're using gfortran from devtoolset then linking to the
libgfortran.so from the base OS is the whole point of devtoolset. New
symbols that aren't in the base libgfortran.so are supposed to be
statically linked into the executable. Please open a bug at
bugzilla.redhat.com about this.
next prev parent reply other threads:[~2021-03-30 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 18:27 Evan Cooch
2021-03-30 15:08 ` Jim Wilson
2021-03-30 15:11 ` Evan Cooch
2021-03-30 15:22 ` Jonathan Wakely [this message]
2021-03-30 16:42 ` Evan Cooch
2021-03-30 17:55 ` Jonathan Wakely
2021-03-30 18:26 ` Evan Cooch
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='CAH6eHdS+vPeGktBNZgwaYea_JmeO6MOf52=bjkt=S+QzsRySdA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=evan.cooch@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jimw@sifive.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).