public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gcc] rhel-f41-base: Small tweaks.
Date: Mon, 29 Jun 2026 12:30:32 GMT [thread overview]
Message-ID: <178273623274.1.3985469065902582270.rpms-gcc-d818c7e53a93@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gcc
Branch : rhel-f41-base
Commit : d818c7e53a93efe1693708367fce1a980d674501
Author : Jakub Jelinek <jakub@redhat.com>
Date : 2024-04-25T12:16:50+02:00
Stats : +13/-5 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gcc/c/d818c7e53a93efe1693708367fce1a980d674501?branch=rhel-f41-base
Log:
Small tweaks.
---
diff --git a/gcc.spec b/gcc.spec
index c0b423c..95e5f0d 100644
--- a/gcc.spec
+++ b/gcc.spec
@@ -1206,8 +1206,12 @@ CONFIGURE_OPTS="\
%endif
%ifarch x86_64
%if 0%{?rhel} > 8
+%if 0%{?rhel} > 9
+ --with-arch_64=x86-64-v3 \
+%else
--with-arch_64=x86-64-v2 \
%endif
+%endif
--with-arch_32=x86-64 \
%endif
%else
@@ -1564,12 +1568,10 @@ for f in `find %{buildroot}%{_prefix}/include/c++/%{gcc_major}/%{gcc_target_plat
done
# Nuke bits/*.h.gch dirs
-# 1) there is no bits/*.h header installed, so when gch file can't be
-# used, compilation fails
-# 2) sometimes it is hard to match the exact options used for building
+# 1) sometimes it is hard to match the exact options used for building
# libstdc++-v3 or they aren't desirable
-# 3) there are multilib issues, conflicts etc. with this
-# 4) it is huge
+# 2) there are multilib issues, conflicts etc. with this
+# 3) it is huge
# People can always precompile on their own whatever they want, but
# shipping this for everybody is unnecessary.
rm -rf %{buildroot}%{_prefix}/include/c++/%{gcc_major}/%{gcc_target_platform}/bits/*.h.gch
@@ -1581,6 +1583,7 @@ cp -r -p ../libstdc++-v3/doc/html ../rpm.doc/libstdc++-v3/html
cp -r -p $libstdcxx_doc_builddir/html ../rpm.doc/libstdc++-v3/html/api
mkdir -p %{buildroot}%{_mandir}/man3
cp -r -p $libstdcxx_doc_builddir/man/man3/* %{buildroot}%{_mandir}/man3/
+rm -f %{buildroot}%{_mandir}/man3/TEMP.*
find ../rpm.doc/libstdc++-v3 -name \*~ | xargs rm
%endif
@@ -3621,6 +3624,11 @@ end
%endif
%changelog
+* Thu Apr 25 2024 Jakub Jelinek <jakub@redhat.com>
+- switch to --with-arch_64=x86-64-v3 for latest RHEL
+- remove obsolete reason for not shipping *.gch* files
+- remove TEMP.* man page from libstdc++-docs
+
* Thu Apr 11 2024 Jakub Jelinek <jakub@redhat.com> 14.0.1-0.15
- update from trunk
- PRs analyzer/114472, c++/114303, c++/114409, debug/112878,
reply other threads:[~2026-06-29 12:30 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=178273623274.1.3985469065902582270.rpms-gcc-d818c7e53a93@fedoraproject.org \
--to=jakub@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