| 1 |
Le 21/06/2020 à 19:06, Michael a écrit : |
| 2 |
>> I need to distribute some linux binaries and the one built with my |
| 3 |
>> up-to-date gentoo sytem won't run on distributions using older glibc. |
| 4 |
>> |
| 5 |
>> My idea is too maintain a gentoo chroot dedicated for compiling my |
| 6 |
>> binaries which would (package.)mask recent versions of glibc and gcc |
| 7 |
>> ebuilds. |
| 8 |
>> |
| 9 |
>> What's the better way to go ? If I start with some of the stage3 |
| 10 |
>> available for download, I won't be able to downgrade the glibc. |
| 11 |
>> |
| 12 |
>> Or do you have any suggestion for alternatives to this gentoo chroot ? |
| 13 |
>> (I'd prefer avoid installing some CentOS or Ubuntu as virtual guests). |
| 14 |
> |
| 15 |
> Once you chroot, you're in the chrooted env. As long as you have a stage 3 |
| 16 |
> old enough to contain the requisite glibc, you should be good to go: |
| 17 |
> |
| 18 |
> http://gentoo.osuosl.org/releases/amd64/ |
| 19 |
> |
| 20 |
|
| 21 |
That's what I did: I found a 2017 stage3 with a still older glibc and |
| 22 |
managed to upgrade to a 2020 gentoo while masking the last glibc |
| 23 |
versions. That was tricky because I had to git-checkout intermediate |
| 24 |
versions of the portage tree in order to deal with the EAPI changes but |
| 25 |
I have a working chroot now. Thanks. |
| 26 |
|
| 27 |
-- |
| 28 |
Hervé |
Archives