| View previous topic :: View next topic |
| Author |
Message |
John Klug
n00b
Joined: 20 Nov 2007
Posts: 51
Location: Minnesota
|
 Posted: Sun Nov 25, 2007 4:46 pm Post subject: wrong compiler in makefile [SOLVED] |
 |
|
I am not sure if this is a portage question or not.
I am trying to build a K6-2 system.
I have purged i386 and i486 compilers and libraries from my system.
I followed the instructions on http://www.gentoo.org/doc/en/change-chost.xml
This was after bootstrap.sh failed with the same problem.
I am guessing that this is the problem. I find this in /usr/lib/python2.4/config/Makefile:
| Quote: | CC= i486-pc-linux-gnu-gcc -pthread
CXX= i486-pc-linux-gnu-g++ -pthread
RANLIB= i486-pc-linux-gnu-ranlib |
/usr/lib/python2.4/config/Makefile is dated 19 Apr 2007, and I have just started with gentoo on this system in the past week.
This is after running
emerge build of pycrypto results in:
| Quote: |
creating build/temp.linux-i586-2.4
creating build/temp.linux-i586-2.4/src
i486-pc-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -march=k6-2 -pipe -fPIC -Isrc/ -I/usr/include/python2.4 -c s
rc/MD2.c -o build/temp.linux-i586-2.4/src/MD2.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 |
I am making an assumption that this is coming from the Makefile above, but I am not certain yet.
How should this be handled with emerge? Should I manually delete /var/tmp/portage/dev-python and call emerge -e system?
I don't want to break the run-time emerge (if it depends on python), so I am afraid of using emerge -C.
/var/lib/portage/world is empty, and I am doing a minimal network install.
Last edited by John Klug on Sun Jan 20, 2008 1:25 pm; edited 1 time in total |
|
| Back to top |
|
 |
mark_alec
Bodhisattva
Joined: 11 Sep 2004
Posts: 5930
Location: Melbourne, Australia
|
| Posted: Sun Nov 25, 2007 10:32 pm Post subject: |
|
|
Moved from Portage & Programming to Installing Gentoo.
If you are trying to install Gentoo on a k6-2, completely install using the i486-stage3 tarball, then change your CHOST as mentioned in the guide. There should be no need to bootstrap, indeed, bootstrapping while changing the CHOST may have caused your failure (it did for me years ago when I was switching between i386  i586)
_________________
www.gentoo.org.au || #gentoo-au |
|
| Back to top |
|
|
John Klug
n00b
Joined: 20 Nov 2007
Posts: 51
Location: Minnesota
|
| Posted: Mon Nov 26, 2007 2:06 am Post subject: wrong compiler in makefile |
|
|
Looking at the stage3-x86-2000.0.tar.bz2 tarball, the original ./usr/lib/python2.4/config/Makefile has the i486 stuff built in.
So unless something in the CHOST instructions rebuilds the Python library Makefile, I may have to run the /usr/lib/python2.4/makesetup manually at some point.
This is the only Makefile in stage3 referencing i486.
The only other makefiles ready to run in Stage 3 are:
./usr/share/groff/1.19.2/font/devps/generate/Makefile
./usr/share/groff/1.19.2/font/devdvi/generate/Makefile
./usr/share/groff/1.19.2/font/devlj4/generate/Makefile
None of the font Makefiles reference gcc.
I am rerunning the CHOST instructions after cleaning out and reloading from the stage3 and the portage snapshot. That will take some time.
My suspicion is that either the stage3 is not quite right, or the CHOST instructions are out of date (like mentioning /usr/lib/python*/makesetup).
I will post again when this completes in a day or two or three. |
|
| Back to top |
|
|
John Klug
n00b
Joined: 20 Nov 2007
Posts: 51
Location: Minnesota
|
| Posted: Sun Dec 09, 2007 3:33 pm Post subject: wrong compiler in makefile |
|
|
Following the CHOST instructions, everything worked until the emerge of world, which failed, with the bad makefile for python.
Then I did and emerge of python (mentioned in the CHOST instructions as an alternative to emerge world), and this fixed the makefile for python with a new configuration.
Then the emerge of world could be resumed. |
|
| Back to top |
|
|
|
Installing Gentoo
