On Wed, 10 Aug 2005, Nicholas Clark wrote:
> On Tue, Aug 09, 2005 at 05:07:40PM -0700, Brezovec, Dick wrote:
> > So do you have any idea of my the script recommended me to abort because
> > I took all the default settings??
> >
> From the output from Configure you quoted in the original bug report,
> the last few lines were reporting about a C compiler failure. However,
> the last line doesn't say that specifically:
>
> You have a BIG problem. Shall I abort Configure [y]
>
> Probably we should add the text
> "I cannot compile programs with your C compiler"
> to that.
Here is the full text of the relevant section:
> Checking your choice of C compiler and flags for coherency...
> I've tried to compile and run the following simple program:
>
> #include <stdio.h>
> int main() { printf("Ok\n"); return(0); }
>
> I used the command:
>
> cc -o try -O try.c -lsocket -lnsl -ldbm -lmalloc -ldl -lld -lm
> -lcrypt -
> lsec -lc -lucb
> ./try
>
> and I got the following output:
>
> ld: fatal: library -ldbm: not found>
> ld: fatal: library -lld: not found
> ld: fatal: library -lucb: not found
> ld: fatal: File processing errors. No output written to try
> I can't compile the test program.
> (The supplied flags or libraries might be incorrect.)
>
> You have a BIG problem. Shall I abort Configure [y]
I think that's pretty self-explanatory. I don't think it can be much
shorter and still give all the relevant information one needs to try to
fix the error.
As others have suggested, using the proper hint file should fix it.
First, it will remove /usr/ucblib from the list of searched
directories. That will take care of the -ldbm and -lucb errors. The
hints file will also tell Configure not to bother with -lld, though I'm
not sure offhand why that was a problem. (My vague recollection is
that -lld would work but was useless and irrelevant for perl on
Solaris.)
--
Andy Dougherty [EMAIL PROTECTED]
