Re: [gentoo-user] Re: Emerge trouble with firefox and thunderbird ...

2024-03-11 Thread Wols Lists

On 10/03/2024 22:44, Carsten Hauck wrote:



The CPU of the machine in question is in deed an old AMD. It's good to
know the reason for that build-failures, thanks a lot.
I certainly will stick to "-clang" in my package.use.


Interesting. I'm not at all sure how old my CPU is, but at four cores it 
must be getting on a bit. Sounds like I should do the same ...


Cheers,
Wol



Re: [gentoo-user] Re: Emerge trouble with firefox and thunderbird ...

2024-03-10 Thread Carsten Hauck

On 10/03/24 at 01:50, mp666 wrote:

On Sat, 9 Mar 2024 08:04:06 +, Wols Lists wrote:


For anyone else who hits this sort of problem, I did an

USE=-clang emerge --update @world

(firefox and thunderbird were the only programs I thought this would
touch), and it worked.

There were a couple of other programs that I guess got pulled in by the
changed use, but they've upgraded which is the main thing.

Thank you very much

Cheers,
Wol


This is a known problem. It generally shows itself with older
architectures like AMD Phenom II, Bulldozer, Intel Core 2 etc.
"-march=native" in the make.conf file was the culprit, IIRC, and replacing
it with core2 or amd's equivalent option solved it. I, instead, put
"-clang" in my package.use file, for firefox. No problem with Firefox
builds since then.




The CPU of the machine in question is in deed an old AMD. It's good to
know the reason for that build-failures, thanks a lot.
I certainly will stick to "-clang" in my package.use.

Greetings,
Carsten



[gentoo-user] Re: Emerge trouble with firefox and thunderbird ...

2024-03-10 Thread mp666
On Sat, 9 Mar 2024 08:04:06 +, Wols Lists wrote:

> For anyone else who hits this sort of problem, I did an
> 
> USE=-clang emerge --update @world
> 
> (firefox and thunderbird were the only programs I thought this would
> touch), and it worked.
> 
> There were a couple of other programs that I guess got pulled in by the
> changed use, but they've upgraded which is the main thing.
> 
> Thank you very much
> 
> Cheers,
> Wol

This is a known problem. It generally shows itself with older 
architectures like AMD Phenom II, Bulldozer, Intel Core 2 etc. 
"-march=native" in the make.conf file was the culprit, IIRC, and replacing 
it with core2 or amd's equivalent option solved it. I, instead, put
"-clang" in my package.use file, for firefox. No problem with Firefox 
builds since then.