[gentoo-user] Still getting calls to gcc-i486

[gentoo-user] Still getting calls to gcc-i486

[Harry Putnam]

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

[Volker Armin Hemmann]

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?

[gentoo-user] Re: Still getting calls to gcc-i486

[Harry Putnam]

Volker Armin Hemmann <volkerarmin@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 <heiko@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

[Volker Armin Hemmann]

On Dienstag 14 Juli 2009, Harry Putnam wrote:
> Volker Armin Hemmann <volkerarmin@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 <heiko@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

[Harry Putnam]

Volker Armin Hemmann <volkerarmin@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.

[gentoo-user] Re: Still getting calls to gcc-i486

[Harry Putnam]

Harry Putnam <reader@newsguy.com> writes:

> 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.

How about it folks... anymore suggestions on this:
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
[...]

So far I haven't found any instance of i486 files remaining on the
system... what else might evoke that output?

CHOST has been i686 for a good while now... thru at least 2 updated
and no problems... but it was once i486... I did all the removal steps
and all the suggestions offered in this thread... but still get the
same error.

Re: [gentoo-user] Re: Still getting calls to gcc-i486

[Heiko Wundram]

On Wed, 15 Jul 2009 16:13:01 -0500, Harry Putnam <reader@newsguy.com>
wrote:
> <snip>
> So far I haven't found any instance of i486 files remaining on the
> system... what else might evoke that output?

As I said: some Python makefile retains the reference to the (former) i486
compiler. That Makefile is used when building packages using distutils
(that's what's happening here). If remerging Python itself didn't help, how
about grepping /usr/lib/python2.6 for "i486", and replacing the matching
string by hand?

grep -R "i486" /usr/lib/python2.6

On my system (i686), it's /usr/lib/python2.6/config/Makefile that matches.
And that should also be what's used by distutils.

-- 
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

[Harry Putnam]

Heiko Wundram <heiko@xencon.net> writes:

> On Wed, 15 Jul 2009 16:13:01 -0500, Harry Putnam <reader@newsguy.com>
> wrote:
>> <snip>
>> So far I haven't found any instance of i486 files remaining on the
>> system... what else might evoke that output?
>
> As I said: some Python makefile retains the reference to the (former) i486
> compiler. That Makefile is used when building packages using distutils
> (that's what's happening here). If remerging Python itself didn't help, how
> about grepping /usr/lib/python2.6 for "i486", and replacing the matching
> string by hand?
>
> grep -R "i486" /usr/lib/python2.6
>
> On my system (i686), it's /usr/lib/python2.6/config/Makefile that matches.
> And that should also be what's used by distutils.

Yup... I didn't quite follow your first post about that.  And assumed
the re-emerge of python under i686 would fix it.

But after editing multiple occurrances of i486 in
/usr/lib/python2.6/config/Makefile ... pycairo now emerges with no
errors.. thanks.

Re: [gentoo-user] Still getting calls to gcc-i486

[Heiko Wundram]

On Tue, 14 Jul 2009 08:40:51 -0500, Harry Putnam <reader@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