When trying to emerge freeradius I get strange errors about 'invalid host type' which appear to be a problem with either the ebuild or one of the configure scripts. Reproducible: Always Steps to Reproduce: 0. (change make.conf to reflect different architecture, but I don't believe this is the issue anymore) 1. emerge freeradius Actual Results: See error msg under Details. Seems strange that it's looking at ${CC} to determine host type, no? Expected Results: Built and installed. ;) configure: configuring in src/modules/rlm_attr_rewrite configure: running /bin/sh './configure' --prefix=/usr '--prefix=/usr' '--sysconfdir=/etc' '--localstatedir=/var' '--mandir=/usr/share/man' '--host=i686-pc-linux-gnu' '--with-gnu-ld' '--with-system-libtool' '--disable-ltdl-install' '--without-snmp' 'CC=gcc' 'CFLAGS=-O2 -march=i686 -pipe' 'host_alias=i686-pc-linux-gnu' --cache-file=/dev/null --srcdir=. configure: warning: CC=gcc: invalid host type configure: warning: CFLAGS=-O2 -march=i686 -pipe: invalid host type configure: error: can only configure for one host and one target at a time configure: error: /bin/sh './configure' failed for src/modules/rlm_attr_rewrite !!! ERROR: net-dialup/freeradius-0.9.3 failed. !!! Function src_compile, Line 86, Exitcode 1 !!! (no error message) </paste> CFLAGS="-O2 -march=athlon-xp -pipe" have also tried with i386 and i686 instead, both from console and by editing make.conf
I've had a friend try this as well, and he gets an identical error. Also note that portage and sync are both up to date..
I can verify this problem. It is a problem with autoconf. The build process with not work with the current version of autoconf (2.58) A workaround is to use the older version of autoconf that is available. This can be accomplished by setting the WANT_AUTOCONF environment variable to 2.1 ("export WANT_AUTOCONF=2.1" if you are using bash) and then issuing the emerge command. The 2.13 version of autoconf seems to work OK. Additionally, this has been broken very recently. I have freeradius 0.9.3 that built successfully on another server sometime in early January without messing around with autoconf. It won't build on that server now.
i added WANT_AUTOMAKE=2.1 for now
