When emerging apache on my O2 and O200, the build failed due to using an old out of date config.guess. The ebuild should use config.guess from /usr/share/gnuconfig which is from sys-devel/gnuconfig.
Steps to Reproduce:
1. emerge apache
checking build system type... build/config.guess: unable to guess system type
This script, last modified 2002-03-20, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from
If the version you run (build/config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <firstname.lastname@example.org> in order to provide the needed
information to handle your system.
config.guess timestamp = 2002-03-20
uname -m = mips64
uname -r = 2.6.6-rc3
uname -s = Linux
uname -v = #75 SMP Wed Apr 28 07:34:48 PDT 2004
/usr/bin/uname -p = R12000 V2.3 FPU V0.0
/bin/uname -X =
/usr/bin/arch -k =
/bin/arch = mips64
UNAME_MACHINE = mips64
UNAME_RELEASE = 2.6.6-rc3
UNAME_SYSTEM = Linux
UNAME_VERSION = #75 SMP Wed Apr 28 07:34:48 PDT 2004
configure: error: cannot guess build type; you must specify one
!!! ERROR: net-www/apache-2.0.49-r1 failed.
!!! Function src_compile, Line 170, Exitcode 1
!!! bad ./configure please submit bug report to bugs.gentoo.org. Include your
It should have used config.guess from /usr/share/gnuconfig.
I dont have a mips box to test this.
Actually, this isn't a bug at all.
mips32 emerge apache
The problem is when running a mips64 kernel, many configure systems have no idea what mips64 is. The mips32 program tricks programs run as arguments to it into thinking the system is really just "mips". For an example how this works, after you emerge mips32, run uname by itself, then run mips32 uname. You can even run "mips32 bash" to get a new shell, and every command run from that shell will be tricked into thinking the system is mips. This is useful if you are going to be emerging a lot of things and don't want any of them to fail on mips64. Anyway, try mips32, and if it still fails to guess the system we'll have to add the gnuconfig tweak to the ebuild. I'm pretty sure mips32 will fix it though. Test and report back...and we'll close the bug.
By the way Dan, have you ever stopped by #gentoo-mips on freenode?
Ok, that worked.
Thanks for the help.
(I'm HydraSwitch on freenode as someone else is using my usual Hydra moniker).
mips32 works, but this still needs some gnuconfig magic done to it (which is the proper fix). I'll add it shortly.
Can you add your gnuconfig magic to 2.0.49-r2 as well. Thanks.
Closing. Please re-open if this is still an issue.