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

Refusing to build binutils when the system version is newer #2817

Open
ocaisa opened this issue Oct 26, 2022 · 2 comments
Open

Refusing to build binutils when the system version is newer #2817

ocaisa opened this issue Oct 26, 2022 · 2 comments
Milestone

Comments

@ocaisa
Copy link
Member

ocaisa commented Oct 26, 2022

In easybuilders/easybuild-easyconfigs#16235 it would seem that the GCC build is failing because the version of binutils using to build glibc is too new compared to the binutils being used in the toolchain. In such a case it is probably best to recommend that the user consider filtering out binutils from the dependencies (at least for that toolchain and any others that use it as a base)

@ocaisa
Copy link
Member Author

ocaisa commented Oct 26, 2022

This could be done as part of the easyblock, where we might refuse to build binutils in this scenario or at least make a BFW warning about the potential issues

@ocaisa ocaisa changed the title Wrapping the system bintuils when it is newer than the version being installed Wrapping the system binutils when it is newer than the version being installed Oct 26, 2022
@ocaisa ocaisa changed the title Wrapping the system binutils when it is newer than the version being installed Refusing to build binutils when it is the system version is newer Oct 26, 2022
@ocaisa ocaisa changed the title Refusing to build binutils when it is the system version is newer Refusing to build binutils when the system version is newer Oct 26, 2022
@boegel boegel added this to the 4.x milestone Nov 9, 2022
@boegel
Copy link
Member

boegel commented Jan 18, 2023

I wouldn't flat out refuse (or at least not without a "trust me, I know what I'm doing" option to opt out), but a big fat warning (ideally with a pointer to a dedicated page/section in the docs) makes sense

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

No branches or pull requests

2 participants