I generally look at the Makefile or configure file and validate that the command can execute... It allows you to test what is wrong, and learn what the script is actually doing.
Personally I think it is cool that some scripts inline a test C file to compile and execute to validate the compiler... Kinda cool. Big Mike On Thu, Mar 04, 2004 at 07:30:10PM -0600, Hmamouche, Youssef wrote: > > my guess is you have to downgrade your c lib. > > you > > On Thu, 4 Mar 2004, Ryan Smith wrote: > > > Has anyone seen this? This is the output from ./configure of xinetd on > > slackware 9.1 2.2.2x kernel. > > <snip> > > checking build system type... i686-pc-linux-gnulibc1 > > checking host system type... i686-pc-linux-gnulibc1 > > checking target system type... i686-pc-linux-gnulibc1 > > checking for gcc... gcc > > checking for C compiler default output... configure: error: C compiler > > cannot create executables > > See `config.log' for more details. > > </snip> > > I'm in the proccess of reinstalling gcc, and all the libraries to be > > sure, but I'm hoping there's a quick fix somewhere out there. > > > > Thanks > > > > > > _______________________________________________ > Siglinux mailing list > [EMAIL PROTECTED] > http://machito.utacm.org/mailman/listinfo/siglinux -- Auto generated sentence : George helps the slippery demon and the worthless cash. _______________________________________________ Siglinux mailing list [EMAIL PROTECTED] http://machito.utacm.org/mailman/listinfo/siglinux
