Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
emerge problems after updating gcc, glibc binutils [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
kinematik
n00b
n00b


Joined: 20 May 2007
Posts: 20
Location: Seville, Spain

PostPosted: Sun Aug 26, 2007 10:47 am    Post subject: emerge problems after updating gcc, glibc binutils [SOLVED] Reply with quote

Since I installed gentoo 2007.0 on my centrino laptop 4 months ago, I could see lot of references to the i486 architecture in the libraries and configuration files. I think maybe I selected the wrong architecture snapshot.

Therefore I updated my gcc, glibc and binutils following this guide:
http://www.gentoo.org/doc/en/change-chost.xml

After this update all the the i486 links and refences were removed, for example variable in /etc/env.d contains now no reference to a i486 architecture like before. This is confirmed by the following commands:

Code:
 
KITOO quino # gcc-config -l
 [1] i686-pc-linux-gnu-4.1.2 *
KITOO quino # binutils-config -l
 [1] i686-pc-linux-gnu-2.17 *


Then I tried to make and emerge world, but two packages are giving an error, and blocking the whole update world process:
Code:
KITOO quino # emerge file

                                  (lot of stuff, and at the end)

make[2]: Entering directory `/var/tmp/portage/sys-apps/file-4.21-r1/work/file-4.21'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/var/tmp/portage/sys-apps/file-4.21-r1/work/file-4.21'
make[1]: Leaving directory `/var/tmp/portage/sys-apps/file-4.21-r1/work/file-4.21'
running build
running build_ext
building 'magic' extension
creating build
creating build/temp.linux-i686-2.4
i486-pc-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -march=pentium-m -O2 -pipe -fomit-frame-pointer -D_GNU_SOURCE -fPIC -I./ -I../ -I../src -I/usr/include/ -I/usr/include/python2.4 -c py_magic.c -o build/temp.linux-i686-2.4/py_magic.o
gcc-config error: Could not run/locate "i486-pc-linux-gnu-gcc"
error: command 'i486-pc-linux-gnu-gcc' failed with exit status 1

!!! ERROR: sys-apps/file-4.21-r1 failed.
Call stack:
  ebuild.sh, line 1638:   Called dyn_compile
  ebuild.sh, line 985:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  file-4.21-r1.ebuild, line 43:   Called distutils_src_compile
  distutils.eclass, line 48:   Called die

!!! compilation failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/sys-apps/file-4.21-r1/temp/build.log'.


The same happens with the samba package. I can see there are some reference to "i486-pc-linux-gnu-gcc" architecture in the error message.

Any clue?, thank you in advanced.


Last edited by kinematik on Mon Aug 27, 2007 4:32 pm; edited 1 time in total
Back to top
View user's profile Send private message
Voltago
Advocate
Advocate


Joined: 02 Sep 2003
Posts: 2561
Location: userland

PostPosted: Sun Aug 26, 2007 11:15 am    Post subject: Reply with quote

Post your
Code:
emerge --info

please.
Back to top
View user's profile Send private message
didymos
Advocate
Advocate


Joined: 10 Oct 2005
Posts: 4798
Location: California

PostPosted: Sun Aug 26, 2007 11:28 am    Post subject: Reply with quote

env.d is not the only place to look. You can end up with leftover symlinks and binaries from the old compiler. Look in /usr/, /usr/libexec/gcc/, /usr/lib/gcc/ for a directory called i486-pc-linux-gnu, and delete it if it exists. Next, do this:
Code:

ls /usr/bin/i486-pc-linux-gnu*


Delete anything you find. Or you can just do this:

Code:

rm -f `ls --color=no /usr/bin/i486-pc-linux-gnu*`


There's probably stuff in /usr/share/gcc-data/i486-pc-linux-gnu as well. That won't cause trouble, but it does waste space. Also, you didn't mention checking /etc/env.d/gcc, so in case you haven't, check for stale files there as well.
_________________
Thomas S. Howard
Back to top
View user's profile Send private message
Genone
Retired Dev
Retired Dev


Joined: 14 Mar 2003
Posts: 9022
Location: beyond the rim

PostPosted: Sun Aug 26, 2007 11:52 am    Post subject: Reply with quote

The given error is probably caused by an old python config file, remerging python might help.
Back to top
View user's profile Send private message
kinematik
n00b
n00b


Joined: 20 May 2007
Posts: 20
Location: Seville, Spain

PostPosted: Mon Aug 27, 2007 4:31 pm    Post subject: Reply with quote

Thank you for all your answers, this is what I did:

First I emerged python as suggested. the following package was installed: dev-lang/python-2.4.4-r4

Second I tried to emerge of the conflictive packages and it worked!. Now I am doing a full world and system update.

I also took a look searching for the old i486 files and symlinks in the suggested directories, finding the following:

Code:

quino@KITOO ~ $ ls /usr/bin/i?86-pc-linux-gnu*
/usr/bin/i486-pc-linux-gnu-c++
/usr/bin/i486-pc-linux-gnu-c++-4.1.1
/usr/bin/i486-pc-linux-gnu-cpp
/usr/bin/i486-pc-linux-gnu-cpp-4.1.1
/usr/bin/i486-pc-linux-gnu-g++
/usr/bin/i486-pc-linux-gnu-g++-4.1.1
/usr/bin/i486-pc-linux-gnu-g++32
/usr/bin/i486-pc-linux-gnu-gcc
/usr/bin/i486-pc-linux-gnu-gcc-4.1.1
/usr/bin/i486-pc-linux-gnu-gcc32
/usr/bin/i486-pc-linux-gnu-gfortran
/usr/bin/i486-pc-linux-gnu-gfortran-4.1.1
/usr/bin/i686-pc-linux-gnu-addr2line
/usr/bin/i686-pc-linux-gnu-ar
/usr/bin/i686-pc-linux-gnu-as
/usr/bin/i686-pc-linux-gnu-c++
/usr/bin/i686-pc-linux-gnu-c++-4.1.2
/usr/bin/i686-pc-linux-gnu-c++filt
/usr/bin/i686-pc-linux-gnu-cpp
/usr/bin/i686-pc-linux-gnu-cpp-4.1.2
/usr/bin/i686-pc-linux-gnu-g++
/usr/bin/i686-pc-linux-gnu-g++-4.1.2
/usr/bin/i686-pc-linux-gnu-gcc
/usr/bin/i686-pc-linux-gnu-gcc-4.1.2
/usr/bin/i686-pc-linux-gnu-gfortran
/usr/bin/i686-pc-linux-gnu-gfortran-4.1.2
/usr/bin/i686-pc-linux-gnu-gprof
/usr/bin/i686-pc-linux-gnu-ld
/usr/bin/i686-pc-linux-gnu-nm
/usr/bin/i686-pc-linux-gnu-objcopy
/usr/bin/i686-pc-linux-gnu-objdump
/usr/bin/i686-pc-linux-gnu-ranlib
/usr/bin/i686-pc-linux-gnu-readelf
/usr/bin/i686-pc-linux-gnu-size
/usr/bin/i686-pc-linux-gnu-strings
/usr/bin/i686-pc-linux-gnu-strip
quino@KITOO ~ $


I removed all of the i486 links and files.

So far I am really enjoying the gentoo experience!.

Best Regards
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum