Summary: | apache-2.0.49-r1 has old config.guess | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dan A. Dickey <dan.dickey> |
Component: | Current packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | major | CC: | mips |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | MIPS | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dan A. Dickey
2004-05-20 05:29:57 UTC
I dont have a mips box to test this. Actually, this isn't a bug at all. Try this: emerge mips32 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. Kumba, Can you add your gnuconfig magic to 2.0.49-r2 as well. Thanks. chuck Closing. Please re-open if this is still an issue. |