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

GCC Snapshots #186

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

GCC Snapshots #186

wants to merge 1 commit into from

Conversation

userdocs
Copy link

Allows the user to specify a gcc snapshot version, from https://gcc.gnu.org/pub/gcc/snapshots, or a mirror of, as the gcc version in the config.mak by setting it as the GCC_VER , for example

GCC_VER = 14-20240310

and use version of gcc to build the toolchain

source: https://git.zv.io/toolchains/musl-cross-make/-/blob/musl.cc/Makefile?ref_type=heads#L67-L68

Allows the user to specify a `gcc` snapshot version, from https://gcc.gnu.org/pub/gcc/snapshots, or a mirror of, as the `gcc` version, like `GCC_VER = 14-20240310` and use this to build the toolchain

source: https://git.zv.io/toolchains/musl-cross-make/-/blob/musl.cc/Makefile?ref_type=heads#L67-L68
@userdocs
Copy link
Author

@richfelker
Copy link
Owner

The problem with this is that mcm explicitly builds toolchains intended to work correctly with musl, which, for most combinations of gcc version and target, means patches are required. I do not want to add as a standard feature an easy way to make toolchains that are subtly broken.

If there were some way to associate with snapshots a base version and apply the patches from that base version and error out if they don't apply unless the user has supplied their own rebased patches, it might make sense to offer this.

@userdocs
Copy link
Author

The archives have a top level dir named gcc-14-20240310/ - would this not be enough to provide patches in a folder named patches/gcc-14-20240310 ?

I figure anyone doing this is in a dev mode anyway and this would be sufficient?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants