A few years ago, I packaged up glibc-arm-linux-gnu, so that Fedora could
have a packaged arm cross-toolchain that was useful (with glibc, it
cannot build anything in userspace). It worked for a while, but lately,
all builds have been failing with this error:
/usr/bin/arm-linux-gnu-ld: skipping incompatible
/usr/lib/gcc/arm-linux-gnueabi/8/libgcc_eh.a when searching for -lgcc_eh
I've looked at it and poked it quite a bit locally, but I can't seem to
get around that. I could really use some help to get this building
again, ideally, updated to 2.28.
All my work is committed to git, no help will be refused.
Thanks in advance,
I've just spotted these when working on Python 3.8.0a1. This happens on 3.7 as
well since GCC 9:
python3-debug.x86_64: E: library-not-linked-against-libc
python3-debug.x86_64: E: library-not-linked-against-libc
python3-libs.x86_64: E: library-not-linked-against-libc
python3-test.x86_64: E: library-not-linked-against-libc
(Note that there are plenty of other extension modules that do not raise this
This doesn't happen with latest python3 built prior to the gcc update to 9.
$ rpmlint -I library-not-linked-against-libc
That isn't helpful either.
I found a similar Debian thing  that says:
> It is theoretically possible to have a library which doesn't use any symbols
> from libc...
Do I care? Should I fix something? I honestly have no idea.
[This proposal was submitted after the deadline. I am announcing it
for community discussion and will leave the decision on whether or not
to grant an exception to FESCo]
== Summary ==
Switch GCC in Fedora 30 to 9.x.y, rebuild all packages with it, or
optionally rebuild just some packages with it and rebuild all packages
only in Fedora 31.
== Owner ==
* Name: [[User:jakub| Jakub Jelínek]]
* Email: jakub(a)redhat.com
== Detailed Description ==
GCC 9 is currently in stage4 since January 7th, in prerelease state
with only regression bugfixes and documentation fixes allowed. The
release will happen probably in the middle of April.
rpms have been built are since today in rawhide.
== Benefit to Fedora ==
See http://gcc.gnu.org/gcc-9/changes.html for the list of changes.
== Scope ==
All packages should be rebuilt with the new gcc once it hits f30, or,
if there is not enough time for that, just all packages built after
the new gcc hits the buildroots.
* Proposal owners:
Build gcc in f30, rebuild packages that have direct dependencies on
exact gcc version (libtool, annobin, gcc-python-plugin).
* Other developers: First few days/weeks just voluntary rebuilds using
the new system gcc, if things fail, look at
http://gcc.gnu.org/gcc-9/porting_to.html and fix bugs in packages or,
if there is a gcc bug or suspected gcc bug, analyze and report.
* Release engineering: . Mass rebuild requested for F30.
* Policies and guidelines: No policies need to be changed
== Upgrade/compatibility impact ==
== How To Test ==
GCC has its own testsuite, which is run during the package build, plus
many other packages with automated tests also help to test the new
== User Experience ==
Users will be able to see compiled code improvements and use the newly
Developers will notice a newer compiler, and might need to adjust
their codebases acording to http://gcc.gnu.org/gcc-9/porting_to.html,
or, if they detect a GCC bug, report it.
== Dependencies ==
libtool, annobin, gcc-python-plugin depend on exact gcc version, those
need to be rebuilt.
== Contingency Plan ==
If bugs are discovered, I'd appreciate help from the package owners in
preparing self-contained testcases to speed up analysis and fixing the
bugs. Don't have time to debug issues in
12000+ packages, especially when in many cases it could be caused by
undefined code in the packages etc. I don't expect we'll have to fall
back to the older gcc, we've never had to do it in the past,
but worst case we can mass rebuild everything with older gcc again.
Jeff Law has performed test mass rebuild on x86_64.
* Contingency mechanism: Revert to older gcc, mass rebuild everything again
* Contingency deadline: Before release
* Blocks release? Yes
* Blocks product? No
== Documentation ==
== Release Notes ==
Fedora 30 comes with GCC 9.1 as primary compiler, see
http://gcc.gnu.org/gcc-9/changes.html for user visible changes in it.
Fedora Program Manager
Do you want to make Fedora 30 better? Please spend 1 minute of your time and try to run:
sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 --enablerepo=updates-testing distro-sync
If you get this prompt:
Total download size: XXX M
Is this ok [y/N]:
you can answer N and nothing happens, no need to test the real upgrade. Upgrades will be fine for you.
But very likely you get some dependency problem now. In that case please report it against appropriate package.
sorry for a slightly off-topic post, but I've noticed that a significant
number of posters is sending HTML e-mail to this list (not to mention
top-replying), which generates unnecessary network traffic. Some people
pay for every bit downloaded, so they're paying for the same information
twice, because the e-mails are sent with multipart/alternative format,
which contains BOTH text/plain and text/html. One thing I noticed those
senders have in common is that they use Gmail.
So, a plea to Gmail users: please stop sending HTML e-mail to Fedora
Dominik (who still reads e-mail in text mode in a terminal)
Fedora https://getfedora.org | RPMFusion http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
The message about Ceph  reminded me that we should probably make the
same notification for Eclipse Platform.
The Eclipse Platform upstream is in the process of dropping all support for
The current state is that upstream are no longer building for 32bit arches
upstream for 4.10 (release 2018-12) onwards. I expect them to start
actively removing 32bit specific code in future releases.
You can read more about the decision on the upstream bug 
In Fedora, Eclipse 4.10 which I am building for Rawhide and F29 right now,
still builds for 32bit arches, but this will not last long. I expect in a
future release (4.11 or later) Eclipse will no longer build on x86/arm and
at that time I will no longer be able to support these architectures in
Fedora -- I expect to exclude those arches from Fedora builds.
If you depend on the ECJ batch compiler, this will continue to be available
on all arches as a noarch package. (It is packaged as a discrete SRPM and
has no build or runtime dependency on the Eclipse Platform itself.)