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

take control over package versions for Prefix bootstrap #132

Open
boegel opened this issue Nov 20, 2021 · 3 comments
Open

take control over package versions for Prefix bootstrap #132

boegel opened this issue Nov 20, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@boegel
Copy link
Contributor

boegel commented Nov 20, 2021

To take control over the exact version that is installed of important packages that are installed in the compat layer when performing the Prefix bootstrap, we can use a package.mask file; see https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Portage#Masked_packages.

This could be important for glibc for example, since using the bleeding-edge version of glibc could cause problems in the software layer, we should probably be a bit more conservative there.

There are known problems with glibc 2.34 (current latest) and the combination of CUDA and GCC 11.x, for example (@amadio: any references on that)?

@boegel boegel added the enhancement New feature or request label Nov 20, 2021
@amadio
Copy link

amadio commented Nov 21, 2021

The bad binutils version has been masked by Sam on prefix. As for glibc, I think that for you it's probably a good idea to mask 2.34 until a newer CUDA has a fix for the problem above. So I believe that with glibc 2.33 and the masked binutils, you should be able to bootstrap now.

@bedroge
Copy link
Collaborator

bedroge commented Nov 26, 2021

Some advice from @amadio on Slack:

  • disable the sync that the bootstrap script does by removing it or by setting auto-sync = no for the gentoo overlay; the latter can be done before starting the bootstrap, but make sure that it doesn' get overwritten.
  • make/use a custom snapshot
  • keep in mind that the layers for the different architectures can still install different versions due to the keywording of packages!
  • test versions using qlist -ICv

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

No branches or pull requests

3 participants