Am Montag, 4. Januar 2021, 13:57:37 EET schrieb Thomas Mueller:
> > > That's what I did: I found a 2017 stage3 with a still older glibc and
> > > managed to upgrade to a 2020 gentoo while masking the last glibc
> > > versions. That was tricky because I had to git-checkout intermediate
> > >
> > That's what I did: I found a 2017 stage3 with a still older glibc and
> > managed to upgrade to a 2020 gentoo while masking the last glibc
> > versions. That was tricky because I had to git-checkout intermediate
> > versions of the portage tree in order to deal with the EAPI changes but
> > I
Am Mittwoch, 1. Juli 2020, 03:30:59 CEST schrieb Thomas Mueller:
> > > That's what I did: I found a 2017 stage3 with a still older glibc and
> > > managed to upgrade to a 2020 gentoo while masking the last glibc
> > > versions. That was tricky because I had to git-checkout intermediate
> > >
> > That's what I did: I found a 2017 stage3 with a still older glibc and
> > managed to upgrade to a 2020 gentoo while masking the last glibc
> > versions. That was tricky because I had to git-checkout intermediate
> > versions of the portage tree in order to deal with the EAPI changes but
> > I
On June 30, 2020 1:26:48 AM PDT, "Andreas K. Huettel"
wrote:
>> That's what I did: I found a 2017 stage3 with a still older glibc and
>> managed to upgrade to a 2020 gentoo while masking the last glibc
>> versions. That was tricky because I had to git-checkout intermediate
>> versions of the
> That's what I did: I found a 2017 stage3 with a still older glibc and
> managed to upgrade to a 2020 gentoo while masking the last glibc
> versions. That was tricky because I had to git-checkout intermediate
> versions of the portage tree in order to deal with the EAPI changes but
> I have a
Le 21/06/2020 à 22:03, Michael a écrit :
I hadn't understood you wanted a current state of an OS, plus current system
and other packages, BUT with a deprecated version of glibc. I thought you
would be OK to use a stage 3 from back then as it was in its totality, frozen
in time, with no
Le 21/06/2020 à 23:08, Rich Freeman a écrit :
On Fri, Jun 19, 2020 at 5:19 PM Hervé Guillemet wrote:
Or do you have any suggestion for alternatives to this gentoo chroot ?
(I'd prefer avoid installing some CentOS or Ubuntu as virtual guests).
You're of course free to do it any way you wish,
On Fri, Jun 19, 2020 at 5:19 PM Hervé Guillemet wrote:
>
> Or do you have any suggestion for alternatives to this gentoo chroot ?
> (I'd prefer avoid installing some CentOS or Ubuntu as virtual guests).
You're of course free to do it any way you wish, but if I wanted to
create packages for
On Sunday, 21 June 2020 20:43:59 BST Hervé Guillemet wrote:
> Le 21/06/2020 à 19:06, Michael a écrit :
> >> I need to distribute some linux binaries and the one built with my
> >> up-to-date gentoo sytem won't run on distributions using older glibc.
> >>
> >> My idea is too maintain a gentoo
Le 21/06/2020 à 19:06, Michael a écrit :
I need to distribute some linux binaries and the one built with my
up-to-date gentoo sytem won't run on distributions using older glibc.
My idea is too maintain a gentoo chroot dedicated for compiling my
binaries which would (package.)mask recent
On Friday, 19 June 2020 22:19:39 BST Hervé Guillemet wrote:
> Hello,
>
> I need to distribute some linux binaries and the one built with my
> up-to-date gentoo sytem won't run on distributions using older glibc.
>
> My idea is too maintain a gentoo chroot dedicated for compiling my
> binaries
Hello,
I need to distribute some linux binaries and the one built with my
up-to-date gentoo sytem won't run on distributions using older glibc.
My idea is too maintain a gentoo chroot dedicated for compiling my
binaries which would (package.)mask recent versions of glibc and gcc
ebuilds.
13 matches
Mail list logo
