[gentoo-amd64] problems with emerging programs

[gentoo-amd64] problems with emerging programs

[Patric Douhane]

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

Hi I,m running a native 64 bit system (which I think is the problem), can anyone with the same hardware (if any) post a copy of their make.conf and other important files? I get "C-compiler cannot create executables" plus sometimes just Errors without a description....been trying to emerge Gnome 7 times now, always some program that fails.....maybe I just should switch to 32/64 system....(but what should I change then?)

New to gnu/linux but works with FreeBSD a little.

Hardware: AMD64 3400+, MSI K8 Neo
march=k8

[-- Attachment #2: Type: text/html, Size: 1066 bytes --]

RE: [gentoo-amd64] problems with emerging programs

[Nadav Horesh]

You have probably set illegal gcc flags.
Which gcc version you have and what are the gcc flags?

  Nadav.

-----Original Message-----
From:	Patric Douhane [mailto:patric@ownit.se]
Sent:	Mon 25-Sep-06 12:39
To:	gentoo-amd64@lists.gentoo.org
Cc:	
Subject:	[gentoo-amd64] problems with emerging programs

Hi I,m running a native 64 bit system (which I think is the problem), can anyone with the same hardware (if any) post a copy of their make.conf and other important files? I get "C-compiler cannot create executables" plus sometimes just Errors without a description....been trying to emerge Gnome 7 times now, always some program that fails.....maybe I just should switch to 32/64 system....(but what should I change then?)

New to gnu/linux but works with FreeBSD a little.

Hardware: AMD64 3400+, MSI K8 Neo
march=k8



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Patric Douhane]

gcc 4.1.1
-march=k8 -02 -pipe


----- Original Message ----- 
From: "Nadav Horesh" <nadavh@visionsense.com>
To: <gentoo-amd64@lists.gentoo.org>; <gentoo-amd64@lists.gentoo.org>
Sent: Monday, September 25, 2006 1:20 PM
Subject: RE: [gentoo-amd64] problems with emerging programs


> You have probably set illegal gcc flags.
> Which gcc version you have and what are the gcc flags?
>
>  Nadav.
>
> -----Original Message-----
> From: Patric Douhane [mailto:patric@ownit.se]
> Sent: Mon 25-Sep-06 12:39
> To: gentoo-amd64@lists.gentoo.org
> Cc:
> Subject: [gentoo-amd64] problems with emerging programs
>
> Hi I,m running a native 64 bit system (which I think is the problem), can 
> anyone with the same hardware (if any) post a copy of their make.conf and 
> other important files? I get "C-compiler cannot create executables" plus 
> sometimes just Errors without a description....been trying to emerge Gnome 
> 7 times now, always some program that fails.....maybe I just should switch 
> to 32/64 system....(but what should I change then?)
>
> New to gnu/linux but works with FreeBSD a little.
>
> Hardware: AMD64 3400+, MSI K8 Neo
> march=k8
>
>
>
> -- 
> gentoo-amd64@gentoo.org mailing list
>
> 


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Petter Haggholm]

That should be -O2 ... the letter O for Optimization [level], not the 
digit 0.

-- 
Petter Häggholm

Patric Douhane wrote:
> gcc 4.1.1
> -march=k8 -02 -pipe

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Patric Douhane]

it is in my computer, just wrong here :)

----- Original Message ----- 
From: "Petter Haggholm" <petter@cs.ubishops.ca>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Monday, September 25, 2006 6:32 PM
Subject: Re: [gentoo-amd64] problems with emerging programs


> That should be -O2 ... the letter O for Optimization [level], not the 
> digit 0.
>
> -- 
> Petter Häggholm
>
> Patric Douhane wrote:
>> gcc 4.1.1
>> -march=k8 -02 -pipe
>
> -- 
> gentoo-amd64@gentoo.org mailing list
>
> 


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Patric Douhane]

Isn't there anyone that can post a make.conf that is using 2006.1, AMD64 
3400+, gcc 4.1.1 and the cflag -march=k8 -O2 -pipe  (preferrably one who's 
system is working properly :)   I'm desperate, soon I will have no choice 
but to reinstall, and I,ve already spent a week to get this far.......

Please also post any other critical files so that I can compare, I would 
post my files but can't copy them since this is another computer.... 


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Joaquim Quinteiro Uchoa]

Without USE (so long to me and not really necessary):

CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j2"
FEATURES=""
ACCEPT_KEYWORDS="~amd64"

# these are to X11 and OpenGL, with ATI card
VIDEO_CARDS="radeon fglrx none"
INPUT_DEVICES="joystick keyboard mouse synaptics"


2006/9/25, Patric Douhane <patric@ownit.se>:
> Isn't there anyone that can post a make.conf that is using 2006.1, AMD64
> 3400+, gcc 4.1.1 and the cflag -march=k8 -O2 -pipe  (preferrably one who's
> system is working properly :)   I'm desperate, soon I will have no choice
> but to reinstall, and I,ve already spent a week to get this far.......
>
> Please also post any other critical files so that I can compare, I would
> post my files but can't copy them since this is another computer....
>
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
[]s
Joaquim
------------------------------------------
  (o_    Joaquim Quinteiro Uchoa
 //\        Consultor Linux e EaD
 U_/_    Linux User # 100534
------------------------------------------
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Patric Douhane]

This is what my make.conf looks like, without all the USE flags and other 
stuff probably not related to my problem.... the big problem I have is that 
I get "segmentation fault" when trying to emerge certain packages from 
Gnome, mozilla-firefox at the moment, but other packages has put out the 
same fault.....
I have also been getting "c-compiler cannot create executables"

> CFLAGS="-march=k8 -O2 -pipe"
> CHOST="x86_64-pc-linux-gnu"
> CXXFLAGS="${CFLAGS}"
> MAKEOPTS="-j2"
> FEATURES="sandbox nostrip"
> ACCEPT_KEYWORDS="amd64"
>

>
>
> 2006/9/25, Patric Douhane <patric@ownit.se>:
>> Isn't there anyone that can post a make.conf that is using 2006.1, AMD64
>> 3400+, gcc 4.1.1 and the cflag -march=k8 -O2 -pipe  (preferrably one 
>> who's
>> system is working properly :)   I'm desperate, soon I will have no choice
>> but to reinstall, and I,ve already spent a week to get this far.......
>>
>> Please also post any other critical files so that I can compare, I would
>> post my files but can't copy them since this is another computer....
>>
>>
>> --
>> gentoo-amd64@gentoo.org mailing list
>>
>>
>
>
> -- 
> []s
> Joaquim
> ------------------------------------------
>  (o_    Joaquim Quinteiro Uchoa
> //\        Consultor Linux e EaD
> U_/_    Linux User # 100534
> ------------------------------------------
> -- 
> gentoo-amd64@gentoo.org mailing list
>
> 


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Piotr Pruszczak]

So, you probably don't have fortran g77 linked to the system or sth like 
this happens during migration from gcc-3.4.x ---->> gcc-4.1.1

that is what I remember happens to me too

post the messages from end of complation please

everybody here wants to help, but we have not too much data from you...

what says #eselect compiler  --list ?

Piotr

Patric Douhane napisał(a):
> This is what my make.conf looks like, without all the USE flags and 
> other stuff probably not related to my problem.... the big problem I 
> have is that I get "segmentation fault" when trying to emerge certain 
> packages from Gnome, mozilla-firefox at the moment, but other packages 
> has put out the same fault.....
> I have also been getting "c-compiler cannot create executables"
> 
>> CFLAGS="-march=k8 -O2 -pipe"
>> CHOST="x86_64-pc-linux-gnu"
>> CXXFLAGS="${CFLAGS}"
>> MAKEOPTS="-j2"
>> FEATURES="sandbox nostrip"
>> ACCEPT_KEYWORDS="amd64"
>>
> 
>>
>>
>> 2006/9/25, Patric Douhane <patric@ownit.se>:
>>> Isn't there anyone that can post a make.conf that is using 2006.1, AMD64
>>> 3400+, gcc 4.1.1 and the cflag -march=k8 -O2 -pipe  (preferrably one 
>>> who's
>>> system is working properly :)   I'm desperate, soon I will have no 
>>> choice
>>> but to reinstall, and I,ve already spent a week to get this far.......
>>>
>>> Please also post any other critical files so that I can compare, I would
>>> post my files but can't copy them since this is another computer....
>>>
>>>
>>> -- 
>>> gentoo-amd64@gentoo.org mailing list
>>>
>>>
>>
>>
>> -- 
>> []s
>> Joaquim
>> ------------------------------------------
>>  (o_    Joaquim Quinteiro Uchoa
>> //\        Consultor Linux e EaD
>> U_/_    Linux User # 100534
>> ------------------------------------------
>> -- 
>> gentoo-amd64@gentoo.org mailing list
>>
>>
> 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Patric Douhane]

hmmm... it says "!!!Error: Can't load module compiler exiting"
I'm guessing that's not good....

----- Original Message ----- 
From: "Piotr Pruszczak" <p.pruszczak@pro.onet.pl>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Monday, September 25, 2006 8:23 PM
Subject: Re: [gentoo-amd64] problems with emerging programs


> So, you probably don't have fortran g77 linked to the system or sth like 
> this happens during migration from gcc-3.4.x ---->> gcc-4.1.1
>
> that is what I remember happens to me too
>
> post the messages from end of complation please
>
> everybody here wants to help, but we have not too much data from you...
>
> what says #eselect compiler  --list ?
>
> Piotr
>
> Patric Douhane napisał(a):
>> This is what my make.conf looks like, without all the USE flags and other 
>> stuff probably not related to my problem.... the big problem I have is 
>> that I get "segmentation fault" when trying to emerge certain packages 
>> from Gnome, mozilla-firefox at the moment, but other packages has put out 
>> the same fault.....
>> I have also been getting "c-compiler cannot create executables"
>>
>>> CFLAGS="-march=k8 -O2 -pipe"
>>> CHOST="x86_64-pc-linux-gnu"
>>> CXXFLAGS="${CFLAGS}"
>>> MAKEOPTS="-j2"
>>> FEATURES="sandbox nostrip"
>>> ACCEPT_KEYWORDS="amd64"
>>>
>>
>>>
>>>
>>> 2006/9/25, Patric Douhane <patric@ownit.se>:
>>>> Isn't there anyone that can post a make.conf that is using 2006.1, 
>>>> AMD64
>>>> 3400+, gcc 4.1.1 and the cflag -march=k8 -O2 -pipe  (preferrably one 
>>>> who's
>>>> system is working properly :)   I'm desperate, soon I will have no 
>>>> choice
>>>> but to reinstall, and I,ve already spent a week to get this far.......
>>>>
>>>> Please also post any other critical files so that I can compare, I 
>>>> would
>>>> post my files but can't copy them since this is another computer....
>>>>
>>>>
>>>> -- 
>>>> gentoo-amd64@gentoo.org mailing list
>>>>
>>>>
>>>
>>>
>>> -- 
>>> []s
>>> Joaquim
>>> ------------------------------------------
>>>  (o_    Joaquim Quinteiro Uchoa
>>> //\        Consultor Linux e EaD
>>> U_/_    Linux User # 100534
>>> ------------------------------------------
>>> -- 
>>> gentoo-amd64@gentoo.org mailing list
>>>
>>>
>>
> -- 
> gentoo-amd64@gentoo.org mailing list
> 


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problems with emerging programs

[Duncan]

"Patric Douhane" <patric@ownit.se> posted
03cb01c6e0d2$61df0e80$7b00a8c0@Turbo2, excerpted below, on  Mon, 25 Sep
2006 20:42:41 +0200:
> ----- Original Message -----
> From: "Piotr Pruszczak" <p.pruszczak@pro.onet.pl> To:
> <gentoo-amd64@lists.gentoo.org>
> Sent: Monday, September 25, 2006 8:23 PM Subject: Re: [gentoo-amd64]
> problems with emerging programs
> 
> 
>> So, you probably don't have fortran g77 linked to the system or sth like
>> this happens during migration from gcc-3.4.x ---->> gcc-4.1.1
>>
>> that is what I remember happens to me too
>>
>> post the messages from end of complation please
>>
>> everybody here wants to help, but we have not too much data from you...
>>
>> what says #eselect compiler  --list ?

> hmmm... it says "!!!Error: Can't load module compiler exiting" I'm
> guessing that's not good....

Top posting corrected...

The compiler module for eselect is masked due to bugs it takes a bit of
work to figure out and work around.  Thus, unless you unmasked it, you'll
have returned to gcc-config, and the above would be entirely expected. 
Therefore, framing the question in terms of gcc-config (I /think/ this is
right, as I'm using eselect-compiler now myself):

What says #gcc-config --list-profiles ?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Patric Douhane]

----- Original Message ----- 
From: "Duncan" <1i5t5.duncan@cox.net>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Monday, September 25, 2006 9:27 PM
Subject: [gentoo-amd64] Re: problems with emerging programs


> "Patric Douhane" <patric@ownit.se> posted
> 03cb01c6e0d2$61df0e80$7b00a8c0@Turbo2, excerpted below, on  Mon, 25 Sep
> 2006 20:42:41 +0200:
>> ----- Original Message -----
>> From: "Piotr Pruszczak" <p.pruszczak@pro.onet.pl> To:
>> <gentoo-amd64@lists.gentoo.org>
>> Sent: Monday, September 25, 2006 8:23 PM Subject: Re: [gentoo-amd64]
>> problems with emerging programs
>>
>>
>>> So, you probably don't have fortran g77 linked to the system or sth like
>>> this happens during migration from gcc-3.4.x ---->> gcc-4.1.1
>>>
>>> that is what I remember happens to me too
>>>
>>> post the messages from end of complation please
>>>
>>> everybody here wants to help, but we have not too much data from you...
>>>
>>> what says #eselect compiler  --list ?
>
>> hmmm... it says "!!!Error: Can't load module compiler exiting" I'm
>> guessing that's not good....
>
> Top posting corrected...
>
> The compiler module for eselect is masked due to bugs it takes a bit of
> work to figure out and work around.  Thus, unless you unmasked it, you'll
> have returned to gcc-config, and the above would be entirely expected.
> Therefore, framing the question in terms of gcc-config (I /think/ this is
> right, as I'm using eselect-compiler now myself):
>
> What says #gcc-config --list-profiles ?
>
        It says "[1] x86_64-pc-linux-gnu-4.1.1 *


> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
> -- 
> gentoo-amd64@gentoo.org mailing list
>
> 


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problems with emerging programs

[Duncan]

"Patric Douhane" <patric@ownit.se> posted
03ec01c6e0da$3dcc4f50$7b00a8c0@Turbo2, excerpted below, on  Mon, 25 Sep
2006 21:38:56 +0200:

>> What says #gcc-config --list-profiles ?
>>
>         It says "[1] x86_64-pc-linux-gnu-4.1.1 *

OK, just to make sure you aren't having the same thing happen that someone
else did -- a missing gcc-4.1.1 even tho that's where the config is
pointed...

What says #gcc -dumpversion ?  (It should say 4.1.1, if it says
3.4.something, you have a problem!)

Beyond that, I'll let the others take over again.  I just jumped in to
straighten out the eselect compiler thing, since I could.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Patric Douhane]

It says 4.1.1 so no luck there....I'm so lost and thinking about switching 
to another dist......but don't really want to give up...

----- Original Message ----- 
From: "Duncan" <1i5t5.duncan@cox.net>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Monday, September 25, 2006 9:53 PM
Subject: [gentoo-amd64] Re: problems with emerging programs


> "Patric Douhane" <patric@ownit.se> posted
> 03ec01c6e0da$3dcc4f50$7b00a8c0@Turbo2, excerpted below, on  Mon, 25 Sep
> 2006 21:38:56 +0200:
>
>>> What says #gcc-config --list-profiles ?
>>>
>>         It says "[1] x86_64-pc-linux-gnu-4.1.1 *
>
> OK, just to make sure you aren't having the same thing happen that someone
> else did -- a missing gcc-4.1.1 even tho that's where the config is
> pointed...
>
> What says #gcc -dumpversion ?  (It should say 4.1.1, if it says
> 3.4.something, you have a problem!)
>
> Beyond that, I'll let the others take over again.  I just jumped in to
> straighten out the eselect compiler thing, since I could.
>
> -- 
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
> -- 
> gentoo-amd64@gentoo.org mailing list
>
> 


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Piotr Pruszczak]

try to :

check IF you have /lib6464 directory if NOT :

dive into /lib64

select ALL

cp * /lib6464 (yes, you should probably temporarily  have /lib6464 
directory )

ldconfig

if you HAVE /lib6464 directory

dive into it #cd /lib6464
cp * /lib64

ldconfig

-------------

presently, I can see I do NOT have /lib6464 in my system, but few days 
ago during the migration I had it and I had to copy some files from it 
into /lib64, however I saw somewhere that somebody had to copy files 
from /lib64 TO /lib6464

seems strange, but for me it started to work ;)
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Patric Douhane]

That didn't help. But I have some more info on my problem though, found this 
line when trying to emerge mozilla-firefox:

"./loadmsgcat.c: 1295: internal compiler error: Segmentation fault"

Hope someone can interprete it...

----- Original Message ----- 
From: "Piotr Pruszczak" <p.pruszczak@pro.onet.pl>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Monday, September 25, 2006 10:30 PM
Subject: Re: [gentoo-amd64] Re: problems with emerging programs


> try to :
>
> check IF you have /lib6464 directory if NOT :
>
> dive into /lib64
>
> select ALL
>
> cp * /lib6464 (yes, you should probably temporarily  have /lib6464 
> directory )
>
> ldconfig
>
> if you HAVE /lib6464 directory
>
> dive into it #cd /lib6464
> cp * /lib64
>
> ldconfig
>
> -------------
>
> presently, I can see I do NOT have /lib6464 in my system, but few days ago 
> during the migration I had it and I had to copy some files from it into 
> /lib64, however I saw somewhere that somebody had to copy files from 
> /lib64 TO /lib6464
>
> seems strange, but for me it started to work ;)
> -- 
> gentoo-amd64@gentoo.org mailing list
>
> 


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Peter Davoust]

Not being as experienced as some users, I reinstall programs when I'm
having trouble (yes, I know it's a bad idea). From my experience
segmentation fault means that there is an error with the code. Try
reinstalling gcc. That's my two cents.

-Peter
On Mon, 2006-09-25 at 23:40 +0200, Patric Douhane wrote:
> That didn't help. But I have some more info on my problem though, found this 
> line when trying to emerge mozilla-firefox:
> 
> "./loadmsgcat.c: 1295: internal compiler error: Segmentation fault"
> 
> Hope someone can interprete it...
> 
> ----- Original Message ----- 
> From: "Piotr Pruszczak" <p.pruszczak@pro.onet.pl>
> To: <gentoo-amd64@lists.gentoo.org>
> Sent: Monday, September 25, 2006 10:30 PM
> Subject: Re: [gentoo-amd64] Re: problems with emerging programs
> 
> 
> > try to :
> >
> > check IF you have /lib6464 directory if NOT :
> >
> > dive into /lib64
> >
> > select ALL
> >
> > cp * /lib6464 (yes, you should probably temporarily  have /lib6464 
> > directory )
> >
> > ldconfig
> >
> > if you HAVE /lib6464 directory
> >
> > dive into it #cd /lib6464
> > cp * /lib64
> >
> > ldconfig
> >
> > -------------
> >
> > presently, I can see I do NOT have /lib6464 in my system, but few days ago 
> > during the migration I had it and I had to copy some files from it into 
> > /lib64, however I saw somewhere that somebody had to copy files from 
> > /lib64 TO /lib6464
> >
> > seems strange, but for me it started to work ;)
> > -- 
> > gentoo-amd64@gentoo.org mailing list
> >
> > 
> 
> 

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Richard Fish]

On 9/25/06, Patric Douhane <patric@ownit.se> wrote:
> That didn't help. But I have some more info on my problem though, found this
> line when trying to emerge mozilla-firefox:
>
> "./loadmsgcat.c: 1295: internal compiler error: Segmentation fault"
>
> Hope someone can interprete it...

Every time I've seen this message on my systems, it has been the
result of flakey hardware, particularly memory.  Nothing stresses the
memory system quite like compiling.

If the system works otherwise, I suspect flaky memory timings.  Try
backing those off (in the BIOS), and see if the problems disappear.

And of course, if you are overclocking anything, stop!

-Richard
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problems with emerging programs

[Duncan]

"Richard Fish" <bigfish@asmallpond.org> posted
7573e9640609251725q52cf39efr58d0f59dfb15ce5b@mail.gmail.com, excerpted
below, on  Mon, 25 Sep 2006 17:25:50 -0700:

> On 9/25/06, Patric Douhane <patric@ownit.se> wrote:
>> That didn't help. But I have some more info on my problem though, found
>> this line when trying to emerge mozilla-firefox:
>>
>> "./loadmsgcat.c: 1295: internal compiler error: Segmentation fault"
>>
>> Hope someone can interprete it...
> 
> Every time I've seen this message on my systems, it has been the result of
> flakey hardware, particularly memory.  Nothing stresses the memory system
> quite like compiling.
> 
> If the system works otherwise, I suspect flaky memory timings.  Try
> backing those off (in the BIOS), and see if the problems disappear.
> 
> And of course, if you are overclocking anything, stop!

100% agreed!  I used to have some borderline generic memory, rated pc3200
(400 MHz), that wasn't quite stable at that.  The trouble was my machine
didn't at that time have a BIOS with memory timing limit capacities, so it
was clocked what it was rated and that was that.

After suffering with it for awhile, I discovered they had a new BIOS
update out which allowed memory timing limits.  Setting it to limit @ 183
MHz (DDRed to 366), I guess PC3000, it was stable as a rock, no problems
whatsoever, until I upgraded to 8 gig awhile later.

Anyway, while it would occasionally freeze the machine, doing whatever,
the worst was bunzip2ing and compiling.  Those would segfault frequently
enough that I had to babysit all my emerges, and learn how to restart in
the middle of them instead of starting over.  So yes, definitely, if gcc
is segfaulting, that's a very strong hint of a hardware problem.

Note that memory is one possibility, but another strong candidate is bad
power, either due to a bad (or underpowered) computer power supply, or in
one case that came up on the lists, an underpowered UPS, or possibly
simply bad incoming power.  So in addition to checking memory, verify your
entire power system, from the wall, thru your UPS (if you don't have one,
try one, but make sure it's high enough powered), thru your computer power
supply itself.  Low power's the equivalent of clocking beyond stable, in
that the effect is occasional zeros where there should be ones.  And yes,
it's gcc and bzip2 (well bunzip2) that seem most sensitive to it.

On the bright side, when there was a problem, gcc would segfault or
there'd be other errors.  I never had an issue with bad builds due to the
memory.  It either built right, or it failed to complete the build at all.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Patric Douhane]

Ok that could be it, though I've never noticed that there could be something 
wrong with the memory before, but I ran Windows XP and perhaps you don't 
notice such problems then? Can I test my memory with Memtest86??

----- Original Message ----- 
From: "Duncan" <1i5t5.duncan@cox.net>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Tuesday, September 26, 2006 8:06 AM
Subject: [gentoo-amd64] Re: problems with emerging programs


> "Richard Fish" <bigfish@asmallpond.org> posted
> 7573e9640609251725q52cf39efr58d0f59dfb15ce5b@mail.gmail.com, excerpted
> below, on  Mon, 25 Sep 2006 17:25:50 -0700:
>
>> On 9/25/06, Patric Douhane <patric@ownit.se> wrote:
>>> That didn't help. But I have some more info on my problem though, found
>>> this line when trying to emerge mozilla-firefox:
>>>
>>> "./loadmsgcat.c: 1295: internal compiler error: Segmentation fault"
>>>
>>> Hope someone can interprete it...
>>
>> Every time I've seen this message on my systems, it has been the result 
>> of
>> flakey hardware, particularly memory.  Nothing stresses the memory system
>> quite like compiling.
>>
>> If the system works otherwise, I suspect flaky memory timings.  Try
>> backing those off (in the BIOS), and see if the problems disappear.
>>
>> And of course, if you are overclocking anything, stop!
>
> 100% agreed!  I used to have some borderline generic memory, rated pc3200
> (400 MHz), that wasn't quite stable at that.  The trouble was my machine
> didn't at that time have a BIOS with memory timing limit capacities, so it
> was clocked what it was rated and that was that.
>
> After suffering with it for awhile, I discovered they had a new BIOS
> update out which allowed memory timing limits.  Setting it to limit @ 183
> MHz (DDRed to 366), I guess PC3000, it was stable as a rock, no problems
> whatsoever, until I upgraded to 8 gig awhile later.
>
> Anyway, while it would occasionally freeze the machine, doing whatever,
> the worst was bunzip2ing and compiling.  Those would segfault frequently
> enough that I had to babysit all my emerges, and learn how to restart in
> the middle of them instead of starting over.  So yes, definitely, if gcc
> is segfaulting, that's a very strong hint of a hardware problem.
>
> Note that memory is one possibility, but another strong candidate is bad
> power, either due to a bad (or underpowered) computer power supply, or in
> one case that came up on the lists, an underpowered UPS, or possibly
> simply bad incoming power.  So in addition to checking memory, verify your
> entire power system, from the wall, thru your UPS (if you don't have one,
> try one, but make sure it's high enough powered), thru your computer power
> supply itself.  Low power's the equivalent of clocking beyond stable, in
> that the effect is occasional zeros where there should be ones.  And yes,
> it's gcc and bzip2 (well bunzip2) that seem most sensitive to it.
>
> On the bright side, when there was a problem, gcc would segfault or
> there'd be other errors.  I never had an issue with bad builds due to the
> memory.  It either built right, or it failed to complete the build at all.
>
> -- 
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
> -- 
> gentoo-amd64@gentoo.org mailing list
> 


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problems with emerging programs

[Duncan]

"Patric Douhane" <patric@ownit.se> posted
04b401c6e136$bacb3140$7b00a8c0@Turbo2, excerpted below, on  Tue, 26 Sep
2006 08:41:00 +0200:

> Ok that could be it, though I've never noticed that there could be
> something wrong with the memory before, but I ran Windows XP and perhaps
> you don't notice such problems then? Can I test my memory with Memtest86??

You can, but it won't necessarily find a problem.  If it does tho, you
know you have one, but on mine, it didn't, because the problem wasn't
really with the memory, but with the speed of access.  Memtest86 came up
100% fine, but it was running on an otherwise idle system (duh, since you
boot to it and can't be running anything else at the time), and simply
wasn't stressing the timings enough to trigger the problem, which as I
said wasn't the memory cells themselves going bad, but simply the timing.

That was part of the frustration.  At first I didn't know which component
it was, and the memory never did actually turn out bad.  It's just that it
wasn't stable at the rated speed when under stress.  I never /did/
actually know it was the memory until I got the BIOS that let me slow it
down, and that cured it -- and then when I got new memory and it ran just
fine at the higher speed, so it wasn't that the mobo memory traces simply
couldn't handle it either.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs

[Richard Fish]

On 9/25/06, Patric Douhane <patric@ownit.se> wrote:
> Ok that could be it, though I've never noticed that there could be something
> wrong with the memory before, but I ran Windows XP and perhaps you don't
> notice such problems then? Can I test my memory with Memtest86??

Not really.  memtest86 can really only tell you if you have bad cells,
which is actually extremely rare.  This is because it works in a very
linear fashion, and only between the CPU and memory.  Compiling
involves random access to different memory cells, rows, and even
pages, as well as DMA transfers to/from the disk[s].

You can find a better script for testing memory here:

http://people.redhat.com/dledford/memtest.html

You might have to make some edits to get it to run on a Gentoo box.

-Richard
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: problems with emerging programs [SOLVED]

[Patric Douhane]

Thanks guys, this solved it! I changed the memory timing in bios, but I also 
disabled "apic", so I really don't know which of them did it, but I will 
re-enable them one at a time to check (later on...)

----- Original Message ----- 
From: "Duncan" <1i5t5.duncan@cox.net>
To: <gentoo-amd64@lists.gentoo.org>
Sent: Tuesday, September 26, 2006 8:06 AM
Subject: [gentoo-amd64] Re: problems with emerging programs


> "Richard Fish" <bigfish@asmallpond.org> posted
> 7573e9640609251725q52cf39efr58d0f59dfb15ce5b@mail.gmail.com, excerpted
> below, on  Mon, 25 Sep 2006 17:25:50 -0700:
>
>> On 9/25/06, Patric Douhane <patric@ownit.se> wrote:
>>> That didn't help. But I have some more info on my problem though, found
>>> this line when trying to emerge mozilla-firefox:
>>>
>>> "./loadmsgcat.c: 1295: internal compiler error: Segmentation fault"
>>>
>>> Hope someone can interprete it...
>>
>> Every time I've seen this message on my systems, it has been the result 
>> of
>> flakey hardware, particularly memory.  Nothing stresses the memory system
>> quite like compiling.
>>
>> If the system works otherwise, I suspect flaky memory timings.  Try
>> backing those off (in the BIOS), and see if the problems disappear.
>>
>> And of course, if you are overclocking anything, stop!
>
> 100% agreed!  I used to have some borderline generic memory, rated pc3200
> (400 MHz), that wasn't quite stable at that.  The trouble was my machine
> didn't at that time have a BIOS with memory timing limit capacities, so it
> was clocked what it was rated and that was that.
>
> After suffering with it for awhile, I discovered they had a new BIOS
> update out which allowed memory timing limits.  Setting it to limit @ 183
> MHz (DDRed to 366), I guess PC3000, it was stable as a rock, no problems
> whatsoever, until I upgraded to 8 gig awhile later.
>
> Anyway, while it would occasionally freeze the machine, doing whatever,
> the worst was bunzip2ing and compiling.  Those would segfault frequently
> enough that I had to babysit all my emerges, and learn how to restart in
> the middle of them instead of starting over.  So yes, definitely, if gcc
> is segfaulting, that's a very strong hint of a hardware problem.
>
> Note that memory is one possibility, but another strong candidate is bad
> power, either due to a bad (or underpowered) computer power supply, or in
> one case that came up on the lists, an underpowered UPS, or possibly
> simply bad incoming power.  So in addition to checking memory, verify your
> entire power system, from the wall, thru your UPS (if you don't have one,
> try one, but make sure it's high enough powered), thru your computer power
> supply itself.  Low power's the equivalent of clocking beyond stable, in
> that the effect is occasional zeros where there should be ones.  And yes,
> it's gcc and bzip2 (well bunzip2) that seem most sensitive to it.
>
> On the bright side, when there was a problem, gcc would segfault or
> there'd be other errors.  I never had an issue with bad builds due to the
> memory.  It either built right, or it failed to complete the build at all.
>
> -- 
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
> -- 
> gentoo-amd64@gentoo.org mailing list
> 


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problems with emerging programs [SOLVED]

[Duncan]

"Patric Douhane" <patric@ownit.se> posted
022201c6e183$94eaf7b0$7b00a8c0@Turbo2, excerpted below, on  Tue, 26 Sep
2006 17:51:07 +0200:

> Thanks guys, this solved it! I changed the memory timing in bios, but I also 
> disabled "apic", so I really don't know which of them did it, but I will 
> re-enable them one at a time to check (later on...)

Good.  One more bug stomped to death! =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problems with emerging programs

[Ronan Klyne]

Piotr Pruszczak wrote:
> So, you probably don't have fortran g77 linked to the system or sth like
> this happens during migration from gcc-3.4.x ---->> gcc-4.1.1
> 

You star! Adding USE=fortran when building gcc sorted no end of
problems, not least of which was the 'C compiler cannot produce valid
compiled c programs' error. Thank you kindly...

	# r
-- 
gentoo-amd64@gentoo.org mailing list