public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Orion Poplawski <orion@cora.nwra.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: Make gcc-gfortran own %{_fmoddir} (#1113564)
Date: Mon, 29 Jun 2026 12:26:56 GMT	[thread overview]
Message-ID: <178273601675.1.9704026293087460368.rpms-gcc-42a3075cdf0d@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gcc
Branch : rhel-f41-base
Commit : 42a3075cdf0d0c32afd10ab0612428a8eef092dc
Author : Orion Poplawski <orion@cora.nwra.com>
Date   : 2016-01-05T19:02:17-07:00
Stats  : +8/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gcc/c/42a3075cdf0d0c32afd10ab0612428a8eef092dc?branch=rhel-f41-base

Log:
Make gcc-gfortran own %{_fmoddir} (#1113564)

---
diff --git a/gcc.spec b/gcc.spec
index 1be34c0..6a0eeeb 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -3,7 +3,7 @@
 %global gcc_version 5.3.1
 # Note, gcc_release must be integer, if you want to add suffixes to
 # %{release}, append them after %{gcc_release} on Release: line.
-%global gcc_release 2
+%global gcc_release 3
 %global _unpackaged_files_terminate_build 0
 %global _performance_build 1
 # Hardening slows the compiler way too much.
@@ -1171,6 +1171,9 @@ rm -f %{buildroot}%{_infodir}/dir
 gzip -9 %{buildroot}%{_infodir}/*.info*
 ln -sf gcc %{buildroot}%{_prefix}/bin/gnatgcc
 
+# Own %%{_fmoddir}
+mkdir -p %{buildroot}%{_fmoddir}
+
 %if %{build_go}
 mv %{buildroot}%{_prefix}/bin/go{,.gcc}
 mv %{buildroot}%{_prefix}/bin/gofmt{,.gcc}
@@ -2619,6 +2622,7 @@ fi
 %{_prefix}/lib/gcc/%{gcc_target_platform}/%{gcc_version}/32/libgfortran.so
 %{_prefix}/lib/gcc/%{gcc_target_platform}/%{gcc_version}/32/finclude
 %endif
+%dir %{_fmoddir}
 %doc rpm.doc/gfortran/*
 
 %files -n libgfortran
@@ -3097,6 +3101,9 @@ fi
 %doc rpm.doc/changelogs/libcc1/ChangeLog*
 
 %changelog
+* Tue Jan  5 2016 Orion Poplawski <orion@cora.nwra.com> 5.3.1-3
+- Make gcc-gfortran own %%{_fmoddir} (#1113564)
+
 * Tue Dec  8 2015 Jakub Jelinek <jakub@redhat.com> 5.3.1-2
 - work around doxygen 1.8.10 bugs (#1279639)
 

                 reply	other threads:[~2026-06-29 12:26 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=178273601675.1.9704026293087460368.rpms-gcc-42a3075cdf0d@fedoraproject.org \
    --to=orion@cora.nwra.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