Since in the forums i had no luck, i am here gcc -march=athlon-xp -O3 -pipe -mmmx -msse -m3dnow -mfpmath=sse -fomit-frame-pointer -o gnome-system-monitor procman.o interface.o callbacks.o load-graph.o proctable.o prettytable.o util.o infoview.o procactions.o procdialogs.o memmaps.o favorites.o -pthread -Wl,--export-dynamic -L/usr/X11R6/lib -L/usr/lib -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lxml2 -lz -lgnomecanvas-2 -lgnome-2 -lart_lgpl_2 -lpangoft2-1.0 -lbonobo-2 -lgnomevfs-2 -lbonobo-activation -lgconf-2 -lORBit-2 -llinc -lgthread-2.0 -lgtop-2.0 -lgtop_sysdeps-2.0 -lgtop_common-2.0 -lwnck-1 -lstartup-notification-1 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 interface.o(.text+0x1f12): In function create_sys_view': : undefined reference to gtk_cell_renderer_progress_new' collect2: ld returned 1 exit status make[2]: *** [gnome-system-monitor] Error 1 make[2]: Leaving directory /var/tmp/portage/gnome-system-monitor-2.0.4-r1/work/gnome-system-monitor- 2.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /var/tmp/portage/gnome-system-monitor-2.0.4-r1/work/gnome-system-monitor-2.0.4' any tips?
does the ebuild for gnome-system-monitor-2.0.4-r1 contain the line 'MAKEOPTS="-j1"' ?
Yeah it does, i commented it out and now it compiles! Patch included
Created attachment 8126 [details, diff] Removes MAKEOPTS from the ebuild
The latest ebuild does still have the MAKEOPTS line. After removing this line I was able to compile gnome-system-monitor.
yeah thats pretty weird huh, the line is ther to ensure that it compiles ( i had reports where it didn't without it) and it shouldn't break builds anyway.
had same issue. removing makeopts -j DID NOT fix it in my case. backing off on compiler optimizations in /etc/make.conf (to -O3 -pipe) DID enable me to compile.
Data point: On my Dual Athlon box, in /etc/make.conf: CFLAGS="-march=athlon-mp -O3 -pipe -fomit-frame-pointer" MAKEOPTS="-j3" Commenting out the MAKEOPTS="-j1" at the tail of gnome-system-monitor-2.0.4-r1.ebuild allowed the build to complete successfully.
What fixed it to me was to remove -fstrict-aliasing from CFLAGS.
Well if you get the error on top here, it seems only to have todo with the order in which things are compiled. -j1 should imo eliminate all possible failures, but it doesn't look that way. I have no idea why some ppl seem to have to disable that to have it compile.
what was exactly the output everyone of you was getting i wonder.
i have disabled the patch for now, but i would like to get it back in so please respond to my previous request. Do whatever you need to recreate the problem :)
noone ?
I recompiled the entire system, and this time -fstrict-aliasing did not cause any problems. I don't know what it could be now...
mm to avoid problems ill leave the patch disabled.. most ppl will now have to wait for gnome2.4 to enjoy this gimmick ;)