static libgfortran linker warnings

static libgfortran linker warnings

[NightStrike]

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?

Re: static libgfortran linker warnings

[Bernhard Reutner-Fischer]

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?

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

Re: static libgfortran linker warnings

[NightStrike]

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.

Re: static libgfortran linker warnings

[Bernhard Reutner-Fischer]

On Wed, 21 Apr 2021 05:29:28 -0400
NightStrike <nightstrike@gmail.com> wrote:

> 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.

gcc/configure.ac suggests that -z ignore / -z record is the native
solaris ld parlance for --as-needed / --no-as-needed
See "AC_CACHE_CHECK(linker --as-needed support".

No idea why your gcc build thought that the ignore/record tuple is the
correct thing to use for as-needed/no-as-needed. Maybe check your
config.log around the '--as-needed support' checks for clues.

I wouldn't suggest to hand edit your libgfortran.spec to use
*lib: %{static-libgfortran:--as-needed} -lquadmath %{static-libgfortran:--no-as-needed} -lm %(libgcc) %(liborig)
but i guess that would silence your linker warnings, too.
HTH,

Re: static libgfortran linker warnings

[Tobias Burnus]

>> 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.

Tobias

-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstrasse 201, 80634 München Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Frank Thürauf

Re: static libgfortran linker warnings

[NightStrike]

On Wed, Apr 21, 2021 at 6:06 AM Bernhard Reutner-Fischer
<rep.dot.nop@gmail.com> wrote:
>
> On Wed, 21 Apr 2021 05:29:28 -0400
> NightStrike <nightstrike@gmail.com> wrote:
>
> > 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.
>
> gcc/configure.ac suggests that -z ignore / -z record is the native
> solaris ld parlance for --as-needed / --no-as-needed
> See "AC_CACHE_CHECK(linker --as-needed support".
>
> No idea why your gcc build thought that the ignore/record tuple is the
> correct thing to use for as-needed/no-as-needed. Maybe check your
> config.log around the '--as-needed support' checks for clues.
>
> I wouldn't suggest to hand edit your libgfortran.spec to use
> *lib: %{static-libgfortran:--as-needed} -lquadmath %{static-libgfortran:--no-as-needed} -lm %(libgcc) %(liborig)
> but i guess that would silence your linker warnings, too.
> HTH,

FWIW:

./ld: supported targets: elf64-x86-64 elf32-i386 elf32-iamcu
elf32-x86-64 pei-i386 pei-x86-64 elf64-l1om elf64-k1om elf64-little
elf64-big elf32-little elf32-big plugin srec symbolsrec verilog tekhex
binary ihex
./ld: supported emulations: elf_x86_64 elf32_x86_64 elf_i386 elf_iamcu
elf_l1om elf_k1om
./ld: emulation specific options:

Re: static libgfortran linker warnings

[NightStrike]

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.