public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Feenberg <feenberg@gmail.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: Tobias Burnus <burnus@net-b.de>, Fortran List <fortran@gcc.gnu.org>
Subject: Re: gfortran static linking under OS X (was: Re: )
Date: Sat, 20 Mar 2021 16:47:03 -0400	[thread overview]
Message-ID: <CAFOAwsoFaKCiaqKtnDNdrJOvBfazmqQKNC=ZtsEzAc88AgO51A@mail.gmail.com> (raw)
In-Reply-To: <3CB88FD5-29C9-48B1-83B7-3E852A8D1029@googlemail.com>

On 3/19/21, Iain Sandoe <idsandoe@googlemail.com> wrote:

>> On Fri, 19 Mar 2021, Tobias Burnus wrote:

>
> you should be able to work around this without changing the compiler or
> rebuilding it,
>
> find
>
> /path/to/compiler/install/lib/libgfortran.spec
>
> make a copy of that (for backup only)
>
> the file contains something like:
>
> #
> # This spec file is read by gfortran when linking.
> # It is used to specify the libraries we need to link in, in the right
> # order.
> #
>
> %rename lib liborig
> *lib:  -lquadmath -lm %(libgcc) %(liborig)
>
> change the last line line to :
>
> *lib: %{!static-libgfortran: -lquadmath } %{static-libgfortran:
> libquadmath.a%s} %(libgcc) %(liborig)
>
> ===
>
> and try your link again
>

Tried that, the error message is:

   ld: library not found for -lSystem

Indeed there is no libsystem.a anywhere on the computer. Any ideas?

Daniel Feenberg

  reply	other threads:[~2021-03-20 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 20:22 Daniel Feenberg
2021-03-19 20:49 ` gfortran static linking under OS X (was: Re: ) Tobias Burnus
2021-03-19 21:06   ` Iain Sandoe
2021-03-19 22:11   ` Daniel Feenberg
2021-03-19 22:39     ` Iain Sandoe
2021-03-20 20:47       ` Daniel Feenberg [this message]
2021-03-20 21:07         ` Iain Sandoe
2021-03-22 22:20           ` Daniel Feenberg

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='CAFOAwsoFaKCiaqKtnDNdrJOvBfazmqQKNC=ZtsEzAc88AgO51A@mail.gmail.com' \
    --to=feenberg@gmail.com \
    --cc=burnus@net-b.de \
    --cc=feenberg@nber.org \
    --cc=fortran@gcc.gnu.org \
    --cc=idsandoe@googlemail.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).