Karl Hammar:
> For testing purposes, I would like to install older compilers,
> e.g. testing with older kernels.
>
> I have tried to install e.g. gcc-5.4.0-r4, gcc-4.9.4, and
> gcc-3.4.6-r2.ebuild (package.unmask is upd. for theese), but it fails.
I have found out that I can install thoose older
On Sun, Dec 02, 2018 at 11:21:55AM +0100, k...@aspodata.se wrote
> so that means I'm on my own.
You can install a *NON*-default gcc in ${HOME} This is a two-step
process. I used to do this a couple of years ago when Pale Moon was
limited in what versions of gcc it would build on. Note that t
Andreas:
> Policy is that you *should* be able to go back in steps of two versions.
> Eg. emerge 4.8 with 5.0 ...
# gcc-config -l
[1] x86_64-pc-linux-gnu-6.4.0 *
[2] x86_64-pc-linux-gnu-7.3.0
#
That means, go from 6.4 -> 6.2 -> 6.0 -> ... ?
But I don't have thoose ebuilds:
$ ls -1 portage/sy
Policy is that you *should* be able to go back in steps of two versions.
Eg. emerge 4.8 with 5.0 ...
However, this is occasionally broken, so please file bugs with the detailed
logs and versions.
Am Freitag, 30. November 2018, 19:25:46 CET schrieb k...@aspodata.se:
> For testing purposes, I wo
For testing purposes, I would like to install older compilers,
e.g. testing with older kernels.
I have tried to install e.g. gcc-5.4.0-r4, gcc-4.9.4, and
gcc-3.4.6-r2.ebuild (package.unmask is upd. for theese), but it fails.
You usually install a newer compiler with the older (and that is
well t
5 matches
Mail list logo
