public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/llvm] rawhide: flang: Add libgcc as requirement
Date: Fri, 24 Jul 2026 19:20:50 GMT	[thread overview]
Message-ID: <178492085081.1.2835044583508051860.rpms-llvm-b1afd798d593@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/llvm
            Branch : rawhide
            Commit : b1afd798d5935a1686536e80e2fcacd512126a76
            Author : Tulio Magno Quites Machado Filho <tuliom@redhat.com>
            Date   : 2026-07-23T13:40:36-03:00
            Stats  : +3/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/llvm/c/b1afd798d5935a1686536e80e2fcacd512126a76?branch=rawhide

            Log:
            flang: Add libgcc as requirement

Most programs compiled by flang link to libgcc. Most of the time we
don't see this because other packages also install libgcc, but some
containers/sandboxes come with a very limited number of packages,
leaving libgcc uninstalled, e.g. TF when testing official packages.

---
diff --git a/llvm.spec b/llvm.spec
index e9d0894..013a11b 100644
--- a/llvm.spec
+++ b/llvm.spec
@@ -1328,6 +1328,9 @@ Requires: %{pkg_name_clang}-resource-filesystem%{?_isa} = %{version}-%{release}
 # flang implicitly calls ld.bfd when linking and depends on the gcc runtime objects.
 Requires: binutils
 Requires: gcc
+# While flang itself does not require libgcc, most programs compiled by flang
+# will need libgcc.
+Requires: libgcc
 # Up to version 17.0.6-1, flang used to provide a flang-devel package.
 # This changed in 17.0.6-2 and all development-related files are now
 # distributed in the main flang package.

                 reply	other threads:[~2026-07-24 19:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178492085081.1.2835044583508051860.rpms-llvm-b1afd798d593@fedoraproject.org \
    --to=tuliom@redhat.com \
    --cc=git-commits@fedoraproject.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