public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/110651] libgfortran.spec links twice with libgcc spec
Date: Fri, 21 Jul 2023 11:39:39 +0000	[thread overview]
Message-ID: <bug-110651-4-AbmUrmrhCA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110651-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110651

--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
>> --- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
>> (In reply to Rainer Orth from comment #0)
>>> When bootstrapping current trunk on macOS 14.0 beta 3 with Xcode 15 beta 4,
>>> every single fortran link test FAILs like
>>
>>> * Get rid of %(libgcc) in libgfortran.spec.in.
>>> 
>>> * Include it conditionally depending on a configure test.
>>
>> Hmm .. I thought we already had configure tests to customise the spec for
>> Darwin?
>> FX?
>
> We do: @LIBM@ is handled that way.

FWIW, I've now removed the %(libgcc) from libgfortran.spec.in locally:
on all of *-*-solaris2.11, x86_64-pc-unix-gnu, and
x86_64-apple-darwin23.0.0 there were no regressions.

It seems ever more important to understand why it was introduced in the
first place, before even considering adding it conditionally.

  parent reply	other threads:[~2023-07-21 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  9:22 [Bug libfortran/110651] New: " ro at gcc dot gnu.org
2023-07-13  9:22 ` [Bug libfortran/110651] " ro at gcc dot gnu.org
2023-07-13  9:30 ` iains at gcc dot gnu.org
2023-07-13  9:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-07-21 11:39 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2023-12-19  8:17 ` fxcoudert at gcc dot gnu.org
2024-02-10 15:48 ` iains at gcc dot gnu.org
2024-02-11 13:53 ` fxcoudert at gcc dot gnu.org

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=bug-110651-4-AbmUrmrhCA@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).