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

update gcc-10 to gcc-13 #97

Closed
ActuallyTheOwner opened this issue Nov 17, 2024 · 2 comments
Closed

update gcc-10 to gcc-13 #97

ActuallyTheOwner opened this issue Nov 17, 2024 · 2 comments

Comments

@ActuallyTheOwner
Copy link

Debian and Gentoo are unable to build this package due to using newer GCC versions
Ubuntu is archaic and very buggy compared to other versions of linux, for the future, please look into Arch linux as an anchor to base packages

@Ortham
Copy link
Member

Ortham commented Nov 18, 2024

I don't really understand the problem: libloot can be built using newer versions of GCC, LOOT's CI uses GCC 12 and the LOOT Flatpak build uses GCC 13.

If this is about the Linux archive that's attached to releases, that's only ever really been intended for use by LOOT's CI (it used to use the libloot release archives), as things like the GCC version and versions of dependencies like ICU make it not really portable between Linux distributions or different versions of distributions.

As for your comment about using Arch, I'm using Ubuntu because that's what GitHub's Actions runners use for their Linux builds, and I'm using a relatively old LTS because there's no need for the libloot CI build to use anything newer - when GitHub eventually remove it from service I'll update to 24.04 or whatever the latest image is at that time.

Since LOOT's CI now builds libloot from source, I'll stop publishing Linux archives with releases, to avoid future confusion.

@Ortham
Copy link
Member

Ortham commented Jan 18, 2025

I've updated CI to use Ubuntu 24.04 and GCC 13 ahead of 20.04's deprecation next month, so I'll close this as done in 0c4bc2f.

@Ortham Ortham closed this as completed Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants