On 06/24 11:12, Daniel Frey wrote:
> On 06/24/18 10:21, Dale wrote:
> > Plus it does say to include that info. If it wasn't provided, it would
> > likely be asked for at some point unless someone has ran into that
> > specific problem and can recognize it with nothing but the bare info.
> >
> > My email program downloaded the whole thing but I don't hold it against
> > someone that is just following instructions. I just wish I knew how to
> > help. :/
> >
> > Dale
> >
> > :-) :-)
> >
>
> Mine downloaded the whole thing too, but I have 150 mbps symmetrical and
> it only took one second to load the message.
>
> Meino, mpfr-4 is marked unstable/testing, is there a specific reason
> you're trying to use it?
>
> You could also refer to:
>
> https://wiki.gentoo.org/wiki/Mpfr4-update-guide
>
> Failing that, you'll probably have to open a bug.
>
> Dan
>
Hi Dan,
thanks for your offered help!
In the past I run Gentoo stable with more headaches than
now running on "un"stable.
mpfr is compiling fine...thats not the problem.
sys-devel/gcc-7.3.0 compiled fine
sys-devel/gcc-7.3.0-r1 compiled fine
sys-devel/gcc-7.3.0-r3 compiled fine (Mon May 21 15:02:26 2018
according to qlop -l
But now it fails in stage 3 as far as I can see for an unknown
(at least for me) reason.
I switched off any optimization in make.conf and tried again
but with no success.
Masking and waiting for the next update does not help since emerge
wants this package and stops any update until I unmask gcc it. That
gives me a nearly full three-stage compilation intro of gcc with
a grande finale: Failed with each sync.
Hmmmm....
Since the unstable packages of today are the stable packages of
tommorrow one needs to bite the bullet (and hopefully this sentence
is not complete nonsense...I am no native speaker...not at all!)
Cheers!
Meino
