public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Philip Kovacs <pkfed@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/slurm] epel10: Use cflag -fcommon to allow for building with gcc 10
Date: Wed, 22 Jul 2026 07:55:18 GMT	[thread overview]
Message-ID: <178470691878.1.4278697757681631273.rpms-slurm-4bfe5d8b9ca6@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/slurm
Branch : epel10
Commit : 4bfe5d8b9ca607b61f1c877312538d8e5b22eea8
Author : Philip Kovacs <pkfed@fedoraproject.org>
Date   : 2020-01-22T11:45:26-05:00
Stats  : +6/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/slurm/c/4bfe5d8b9ca607b61f1c877312538d8e5b22eea8?branch=epel10

Log:
Use cflag -fcommon to allow for building with gcc 10

---
diff --git a/slurm.spec b/slurm.spec
index b4f887a..15e53ff 100644
--- a/slurm.spec
+++ b/slurm.spec
@@ -16,7 +16,7 @@
 
 Name:           slurm
 Version:        19.05.5
-Release:        1%{?dist}
+Release:        2%{?dist}
 Summary:        Simple Linux Utility for Resource Management
 License:        GPLv2 and BSD
 URL:            https://slurm.schedmd.com/
@@ -236,6 +236,8 @@ cp %SOURCE5 extras/%{name}-setuser.in
 aclocal -I auxdir
 autoconf
 automake --no-force
+# use -fcommon for gcc 10 to avoid multiple definition errors
+export CFLAGS="%{build_cflags} -fcommon"
 # use -z lazy to allow dlopen with unresolved symbols
 export LDFLAGS="%{build_ldflags} -Wl,-z,lazy"
 %configure \
@@ -692,6 +694,9 @@ rm -f %{buildroot}%{perl_archlib}/perllocal.pod
 %systemd_postun_with_restart slurmdbd.service
 
 %changelog
+* Wed Jan 22 2020 Philip Kovacs <pkfed@fedoraproject.org> - 19.05.5-2
+- Use cflag -fcommon to allow for building with gcc 10
+
 * Mon Dec 23 2019 Philip Kovacs <pkfed@fedoraproject.org> - 19.05.5-1
 - Release of 19.05.5
 - Closes security issues CVE-2019-19727, CVE-2019-19728

                 reply	other threads:[~2026-07-22  7:55 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=178470691878.1.4278697757681631273.rpms-slurm-4bfe5d8b9ca6@fedoraproject.org \
    --to=pkfed@fedoraproject.org \
    --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