Alan McKinnon wrote:
On Sunday 18 January 2009 06:38:15 Richard Watson wrote:
I'm sorry about the delay in closing this. I finally figured out if I
remove "-pipe" from my /etc/make.conf CFLAGS that all my compile errors go
away. Looking at the reference on the subject this option tells GCC not to
create temporary files when compiling but to turn this off if low on RAM.
Not sure why this happens as I have a 1GB Ram. Maybe this is not enough
these days. Anyway problem solved.
That's an interesting result, but I can't help thinking it's the wrong
solution to the wrong problem. One of my machines has had merely 1G for 2
years, before that it had 512M for 3 years and it has never shown this
symptom. I have servers at work with 512M - same thing, even when building
current packages.
Gut feel is telling me that removing -pipe is simply revealing a deeper
symptom somewhere - 1G is actually an enormous amount of memory for
compilation purposes. If you feel like digging deeper, I'd be very interested
to see where this one leads.
I would like to write my first post here just to inform you that I also
had this problem with avahi and pygtk.
Avahi failed to emerge and I had to remove pygtk from my use flags, than
it compiled OK.
I was just interested if removing "-pipe" from CFLAGS makes any
difference, and I tried remove it and emerge avahi with pygtk, but it
does not compile.
For me it compiles only without pygtk and changing -pipe doesn't work at
all. I checked this because I have 512M.
I don't know why I might need avahi with pygtk...disabling pygtk use
flag for avahi works fine and other packages compile well.
Wojtek
