On Fri, Mar 28, 2008 at 09:59:46PM +0700, [EMAIL PROTECTED] wrote: > configure:2185: checking for suffix of executables > configure:2187: cc -o conftest -O2 -fno-strict-aliasing -pipe conftest.c > >&5 > cc: conftest.c: No such file or directory > cc: No input files specified > configure:2190: $? = 1 > configure:2207: error: cannot compute suffix of executables: cannot compile > and link > See `config.log' for more details.
The problem is here. For some particular reason, there's no conftest.c available to the compiler. I'm pretty sure configure scripts create this file themselves, then try to compile it. There's also the possibility of "autoconf" being required and run, which would build the configure script itself, and that might be broken. It's possible the autoconf* installation on your machine is outdated, or is incompatible with the version the software was developed around. All that's in net/traffic/Makefile is: GNU_CONFIGURE= yes So the question is why configure isn't creating conftest.c; possibly an old autoconfs port installation? If conftest.c comes with the software already, then I have no explanation for what's going on. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
