From: NightStrike <nightstrike@gmail.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: NightStrike via Fortran <fortran@gcc.gnu.org>
Subject: Re: static libgfortran linker warnings
Date: Wed, 21 Apr 2021 05:29:28 -0400 [thread overview]
Message-ID: <CAF1jjLvXgjcXK+gARx7z-8s2bZ4CAbdn8z=eVUt8C_QLVdQzFw@mail.gmail.com> (raw)
In-Reply-To: <20210421105902.49cc7ef3@nbbrfq>
On Wed, Apr 21, 2021 at 4:59 AM Bernhard Reutner-Fischer
<rep.dot.nop@gmail.com> wrote:
> On Wed, 21 Apr 2021 02:34:43 -0400
> NightStrike via Fortran <fortran@gcc.gnu.org> wrote:
>
> > When linking with -static-libgfortran, I get warnings from ld of the form
> > "ld: warning: -z ignore ignored" and "ld: warning: -z record ignored". I
> > can't find those -z options documented anywhere. Why is gfortran adding
> > them?
>
> -z are options to ld.
> Which linker do you use, on which OS?
binutils 2.32 (stock build from source) on CentOS 7.
> If you use binutils, you can pass -Wl,--verbose to the compiler to
> instruct the linker to dump the linker script while linking. This should
> show where the -z comes from:
> gfortran foo.f90 -static-libgfortran -Wl,--verbose
I didn't do this per se, but I did gfortran -v, and saw that it was an
option to collect2. I can try your method when the system is
available again tomorrow.
next prev parent reply other threads:[~2021-04-21 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 6:34 NightStrike
2021-04-21 8:59 ` Bernhard Reutner-Fischer
2021-04-21 9:29 ` NightStrike [this message]
2021-04-21 10:06 ` Bernhard Reutner-Fischer
2021-04-21 21:24 ` NightStrike
2021-04-21 10:16 ` Tobias Burnus
2021-04-21 21:34 ` NightStrike
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='CAF1jjLvXgjcXK+gARx7z-8s2bZ4CAbdn8z=eVUt8C_QLVdQzFw@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=rep.dot.nop@gmail.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).