Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libgcc toolchain mismatch #189

Open
m2Giles opened this issue Aug 24, 2024 · 5 comments
Open

libgcc toolchain mismatch #189

m2Giles opened this issue Aug 24, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@m2Giles
Copy link
Member

m2Giles commented Aug 24, 2024

The gcc toolchain has a mismatch of versions installed. libgomp has a prerelease version installed while all other portions of the toolchain are the latest release.

This prevents gcc and other parts of the toolchain from getting installed.

@dosubot dosubot bot added the bug Something isn't working label Aug 24, 2024
@bsherman
Copy link
Collaborator

rpm -q libgcc
libgcc-14.1.1-7.fc40.x86_64

libgcc seems to come from here: https://github.com/coreos/fedora-coreos-config/blob/stable/manifest-lock.x86_64.json#L1287-L1291

    "libgcc": {
      "evra": "14.1.1-7.fc40.x86_64",
      "metadata": {
        "sourcerpm": "gcc"
      }

This is a fixed version, older than what is current in Fedora... libgomp is actually current.

This is exactly the kind of problem I previously attempted to fix by using the fedora-coreos-pool repo which sources direct from koji back in #167

I don't think we recommend users install gcc direct on a CoreOS install, as that should be done in distrobox, etc...

@m2Giles are you trying to install gcc at build time or something? we could temporarily add the fedora-coreos-pool repo, but if it's left in place globally, pre-release (even fc41) packages are improperly installed, thus #178 to remove that repo.

@m2Giles
Copy link
Member Author

m2Giles commented Aug 25, 2024

I was trying to install gcc as part of using brew. But the actual issue that identified it was Antheas rechunk needs them to have same package version.

@bsherman
Copy link
Collaborator

I was trying to install gcc as part of using brew. But the actual issue that identified it was Antheas rechunk needs them to have same package version.

For context, rechunk ...

@m2Giles maybe you have a build log I can review? I'm not 100% sure what you are telling me. I think it's a generic problem with the way coreos pins its rpm versions and doesn't provide a yum repo which provides the pinned version, but, with rechunker in the mix, I'm confused.

I don't see how we're ever going to have the "same version" in a coreos based image for gcc, given the coreos pinning strategy.

@antheas
Copy link

antheas commented Aug 28, 2024

I was trying to install gcc as part of using brew. But the actual issue that identified it was Antheas rechunk needs them to have same package version.

I think you are referring to this fix:
https://github.com/hhd-dev/rechunk/releases/tag/v0.8.4

It was caused by an uncaught logic error due to the image being too small...

@bsherman
Copy link
Collaborator

I think you are referring to this fix: https://github.com/hhd-dev/rechunk/releases/tag/v0.8.4

It was caused by an uncaught logic error due to the image being too small...

Oh! It would be great if the rechunker side of this is already fixed or a non-issue. I do want to try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants