View previous topic :: View next topic |
Author |
Message |
kshade n00b
Joined: 13 Jan 2004 Posts: 60 Location: Germany
|
Posted: Wed Mar 10, 2004 12:14 pm Post subject: iputils won't emegre |
|
|
iputils stop configuring with Quote: | checking build system type... Invalid configuration 'x86_64-unknown-linux-gnu' not recognized | Quote: | !!! Function econf, line 365, Exitcode 1 |
My make.conf:[quote]CFLAGS="-03"
CHOST="x86_64-pc-linux-gnu"
USE=""
CXXFLAGS="$CFLAGS"
ACCEPT_KEYWORDS="~amd64" |
|
Back to top |
|
|
sheepdog Guru
Joined: 14 Oct 2002 Posts: 369 Location: Edison Enterprises Inc., Lake Oswego, Oregon, USA
|
Posted: Wed Mar 10, 2004 10:25 pm Post subject: |
|
|
I have experienced something like this with another ebuild. The problem was the the config.sub file had not been updated to included the latest amd64 types. What I did was add a line to the ebuild like this: Code: | cp /usr/share/gnuconfig/config.sub . | so that the source_compile section of the ebuild looks like Code: | src_compile() {
cp /usr/share/gnuconfig/config.sub .
econf || die
emake || die "emake failure"
} |
This then gives the autoconf system the latest machine types. I'm not sure this will solve your problem though since my ebuild was complaining about an undefined "host" type, not a build system type. Furthermore, I have iputils emerged and did not experience your difficulty. Hope it helps.
By the way. Take the line Code: | ACCEPT_KEYWORDS="~amd64" | out of your make.conf. It will cause you much trouble. Unmask each ebuild individually as you go along. Otherwise you will end up with a version of glibc that has been masked for amd64 because it hasn't been shown to work, while there is one already unmasked specifically for amd64. Unless you really want to build a bleeding-edge test system, of course. |
|
Back to top |
|
|
|
|
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
|
|