From: NightStrike <nightstrike@gmail.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Subject: Re: static libgfortran linker warnings
Date: Wed, 21 Apr 2021 17:34:58 -0400 [thread overview]
Message-ID: <CAF1jjLtMg+Mi9vtHUyCYWDLdVT=raOEbpBqOKaZd2CLAw7etvQ@mail.gmail.com> (raw)
In-Reply-To: <be94823e-bc50-2c7c-bb84-cce0e7b20fa1@codesourcery.com>
On Wed, Apr 21, 2021 at 6:17 AM Tobias Burnus <tobias@codesourcery.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.
>
> libgfortran/acinclude.m4 contains:
>
> dnl Check whether -Wl,--as-needed resp. -Wl,-zignore is supported
>
> That's where -z could come from. – Could you check what is in the
> installed file libgfortran.spec? On my Linux, it has:
>
> %{static-libgfortran:--as-needed}
>
> If you have a '-z ignore' there, it would be interesting to understand
> why – and what 'libgfortran/config.log' shows.
>
> >> Which linker do you use, on which OS?
> > binutils 2.32 (stock build from source) on CentOS 7.
>
> Here: Ubuntu with binutils 2.34.
%rename lib liborig
*lib: %{static-libgfortran:-zignore} -lquadmath
%{static-libgfortran:-zrecord} -lm %(libgcc) %(liborig)
Clearly, I built it wrong. I just would like to know how I did so.
prev parent reply other threads:[~2021-04-21 21:35 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
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 [this message]
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='CAF1jjLtMg+Mi9vtHUyCYWDLdVT=raOEbpBqOKaZd2CLAw7etvQ@mail.gmail.com' \
--to=nightstrike@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=rep.dot.nop@gmail.com \
--cc=tobias@codesourcery.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).