[gentoo-user] Suggestion for cflags for intel xeon 5500 processors
Hi, Does anyone have any suggestions for CFLAGS settings in make.conf for an Intel Xeon 5500 series processor? Should I use -march=core2 or nocona or native? I am starting a fresh install of Gentoo on a new machine. Thanks in advance. Denis
Re: [gentoo-user] Suggestion for cflags for intel xeon 5500 processors
On Tuesday 14 July 2009 11:37:49 denis cohen wrote: Hi, Does anyone have any suggestions for CFLAGS settings in make.conf for an Intel Xeon 5500 series processor? Should I use -march=core2 or nocona or native? I am starting a fresh install of Gentoo on a new machine. Thanks in advance. Is this a fresh unstable install? If so, your gcc will be recent and you should use march=native Let the software figure it out. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Suggestion for cflags for intel xeon 5500 processors
On Tue, 14 Jul 2009 13:37:21 +0200, Alan McKinnon wrote: Should I use -march=core2 or nocona or native? I am starting a fresh install of Gentoo on a new machine. Thanks in advance. Is this a fresh unstable install? If so, your gcc will be recent and you should use march=native Unless you use distcc -- Neil Bothwick Remember, it takes 47 muscles to frown And only 4 to pull the trigger of a sniper rifle signature.asc Description: PGP signature
Re: [gentoo-user] Suggestion for cflags for intel xeon 5500 processors
On Tue, Jul 14, 2009 at 14:24, Neil Bothwickn...@digimed.co.uk wrote: On Tue, 14 Jul 2009 13:37:21 +0200, Alan McKinnon wrote: Should I use -march=core2 or nocona or native? I am starting a fresh install of Gentoo on a new machine. Thanks in advance. Is this a fresh unstable install? If so, your gcc will be recent and you should use march=native Unless you use distcc It's a fresh install but have never used unstable version. Would gcc stable version 4.3.2-r3 work with using 'march=native'? Won't be using distcc. Denis
[gentoo-user] Still getting calls to gcc-i486
On a recent update world I get a failure on pycairo that appears to be the result of a call for gcc-i486. A month or more ago I went thru the process of changing /etc/make.conf from i486 to i686... deleting all instances of files with i486. I've lost track of where all the guff was located but apparently I missed something can anyone tell me where to look? emerge error: [...] building 'cairo._cairo' extension creating build/temp.linux-i686-2.6 creating build/temp.linux-i686-2.6/cairo i486-pc-linux-gnu-gcc -pthread -DNDEBUG -O2 -march=i686 -pipe -fPIC -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/python2.6 -c cairo/cairomodule.c -o build/temp.linux-i686-2.6/cairo/cairomodule.o unable to execute i486-pc-linux-gnu-gcc: No such file or directory error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 [...]
Re: [gentoo-user] Still getting calls to gcc-i486
On Dienstag 14 Juli 2009, Harry Putnam wrote: On a recent update world I get a failure on pycairo that appears to be the result of a call for gcc-i486. A month or more ago I went thru the process of changing /etc/make.conf from i486 to i686... deleting all instances of files with i486. I've lost track of where all the guff was located but apparently I missed something can anyone tell me where to look? emerge error: [...] building 'cairo._cairo' extension creating build/temp.linux-i686-2.6 creating build/temp.linux-i686-2.6/cairo i486-pc-linux-gnu-gcc -pthread -DNDEBUG -O2 -march=i686 -pipe -fPIC -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/python2.6 -c cairo/cairomodule.c -o build/temp.linux-i686-2.6/cairo/cairomodule.o unable to execute i486-pc-linux-gnu-gcc: No such file or directory error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 [...] did you run fix-libtool.sh?
Re: [gentoo-user] Still getting calls to gcc-i486
On Tue, 14 Jul 2009 08:40:51 -0500, Harry Putnam rea...@newsguy.com wrote: I've lost track of where all the guff was located but apparently I missed something can anyone tell me where to look? emerge error: [...] building 'cairo._cairo' extension creating build/temp.linux-i686-2.6 creating build/temp.linux-i686-2.6/cairo i486-pc-linux-gnu-gcc -pthread -DNDEBUG -O2 -march=i686 -pipe -fPIC -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/python2.6 -c cairo/cairomodule.c -o build/temp.linux-i686-2.6/cairo/cairomodule.o unable to execute i486-pc-linux-gnu-gcc: No such file or directory error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 [...] Re-merge python. Python keeps the compiler that was used to compile it in a separate Makefile that's used to compile Python packages (with distutils), and that's what you're hitting here (as you haven't updated that). -- Heiko Wundram Gehrkens.IT GmbH FON 0511-59027953 | http://www.gehrkens.it FAX 0511-59027957 | http://www.xencon.net Gehrkens.IT GmbH Strasse der Nationen 5 30539 Hannover Registergericht: Amtsgericht Hannover, HRB 200551 Geschäftsführer: Harald Gehrkens, Daniel Netzer
[gentoo-user] Re: Still getting calls to gcc-i486
Volker Armin Hemmann volkerar...@googlemail.com writes: [...] i486-pc-linux-gnu-gcc: No such file or directory error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 [...] did you run fix-libtool.sh? Doing so failed to help in any way. root # fix_libtool_files.sh `gcc -dumpversion` --oldarch i486-pc-linux-gnu * Scanning libtool files for hardcoded gcc library paths... * [1/5] Scanning /lib ... * [2/5] Scanning /usr/lib ... * [3/5] Scanning //usr//lib/opengl/xorg-x11/lib ... * [4/5] Scanning /usr/i686-pc-linux-gnu/lib ... * [5/5] Scanning /usr/local/lib ... Looks like nothing was found. reemerge pycairo fails with same error Heiko Wundram he...@xencon.net writes: [...] unable to execute i486-pc-linux-gnu-gcc: No such file or directory error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 [...] Re-merge python. Python keeps the compiler that was used to compile it in a separate Makefile that's used to compile Python packages (with distutils), and that's what you're hitting here (as you haven't updated that). That went off without error, but then going back to update world fails at pycairo with same error message.
Re: [gentoo-user] Re: Still getting calls to gcc-i486
On Dienstag 14 Juli 2009, Harry Putnam wrote: Volker Armin Hemmann volkerar...@googlemail.com writes: [...] i486-pc-linux-gnu-gcc: No such file or directory error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 [...] did you run fix-libtool.sh? Doing so failed to help in any way. root # fix_libtool_files.sh `gcc -dumpversion` --oldarch i486-pc-linux-gnu * Scanning libtool files for hardcoded gcc library paths... * [1/5] Scanning /lib ... * [2/5] Scanning /usr/lib ... * [3/5] Scanning //usr//lib/opengl/xorg-x11/lib ... * [4/5] Scanning /usr/i686-pc-linux-gnu/lib ... * [5/5] Scanning /usr/local/lib ... Looks like nothing was found. reemerge pycairo fails with same error Heiko Wundram he...@xencon.net writes: [...] unable to execute i486-pc-linux-gnu-gcc: No such file or directory error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1 [...] Re-merge python. Python keeps the compiler that was used to compile it in a separate Makefile that's used to compile Python packages (with distutils), and that's what you're hitting here (as you haven't updated that). That went off without error, but then going back to update world fails at pycairo with same error message. you could grep for i486-pc-linux-gnu-gcc
[gentoo-user] Re: Still getting calls to gcc-i486
Volker Armin Hemmann volkerar...@googlemail.com writes: That went off without error, but then going back to update world fails at pycairo with same error message. you could grep for i486-pc-linux-gnu-gcc I'm not sure what you had in mind there... or where to grep -r but a grep -r from `/' has run for several hours and turned up nothing. I finished the update world by using --skip-first but with the update done, going back to pycairo... it still fails exactly the same. Can you be a little more specific about what you are thinking with the grep idea? Also ... anyone have another idea how to iron this out. I've done everything suggested here in this thread but still cannot compile pycairo successfully. Do I really need it... what other operations might use it? Using the `-t' flag to emerge like `-vpuDt world' shows a chain of stuff related to emacs-cvs: These are the packages that would be merged, in reverse order: Calculating dependencies... done! [nomerge ] app-editors/emacs-cvs-23.0.96 USE=X alsa gif gpm svg xpm -Xaw3d -dbus -gtk -gzip-e l -hesiod -jpeg -kerberos -m17n-lib -motif -png -sound -source -tiff -toolkit-scroll-bars -xft [nomerge ] gnome-base/librsvg-2.26.0 USE=zlib -debug -doc [nomerge ] gnome-extra/libgsf-1.14.15 USE=bzip2 python -debug -doc -gnome [nomerge ] dev-python/pygtk-2.14.1 USE=X -doc -examples [ebuild U ] dev-python/pycairo-1.8.6 [1.8.4] USE=-doc% -examples 0 kB But I'd sooner find why i486 gcc is getting involved.
