|
From: | Ray Kolbe |
Subject: | Re: [bug-inetutils] unable to build inetutils on sparc solaris |
Date: | Wed, 02 Jun 2004 08:57:43 -0700 |
User-agent: | Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 |
Well, I didn't send the exact same email. Whatever.I'm simply attempting to build this software and it fails every time! No matter which compiler I use!
I have built emacs, and that works just fine. I have built other software packages, but this one fails! My build of gimp also failed, but it gave me information to identify why it failed, which this software does NOT do.
I'll try once more. Here are some error messages: > make make all-recursive Making all in headers Making all in libinetutils source='xmalloc.c' object='xmalloc.o' libtool=no \ depfile='.deps/xmalloc.Po' tmpdepfile='.deps/xmalloc.TPo' \ depmode=none /bin/bash ../depcomp \cc -DHAVE_CONFIG_H -I. -I. -I.. -DPATH_TTY_PFX=\"/dev/\" -DPATH_DEVNULL=\"/dev/null\" -I../include -g -c `test -f 'xmalloc.c' || echo './'`xmalloc.c
"xmalloc.c", line 37: cannot find include file: "error.h" "xmalloc.c", line 70: warning: implicit function declaration: error cc: acomp failed for xmalloc.c *** Error code 2 make: Fatal error: Command failed for target `xmalloc.o' Current working directory /usr/share/inetutils-1.4.2/libinetutils *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /usr/share/inetutils-1.4.2 *** Error code 1 make: Fatal error: Command failed for target `all'
From: "Alfred M. Szmidt" <address@hidden> To: Ray Kolbe <address@hidden> Cc: address@hidden Subject: Re: [bug-inetutils] unable to build inetutils on sparc solaris Date: Wed, 02 Jun 2004 10:46:26 +0200 You know, it is quite rude to send the _exact_ same mail, which is quite big _twice_. I ask again, what are the errors, cause the I, nor anyone else is going to weed through 100k of log output which is, infact, totally useles. Why is it useless? It is supposed to have errors in it, it is the configure script checking for the behaviour of the compiler. So if function foo() doesn't exist, the compiler will barf, and configure will see that this fucntion does not exist on your system. And to prove my point that the configure script ran sucessfull, look at the last line of your ouput.
[Prev in Thread] | Current Thread | [Next in Thread] |