bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug report as requested.


From: Ralf Wildenhues
Subject: Re: Bug report as requested.
Date: Wed, 10 Jan 2007 19:05:27 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

* Hugh Sasse wrote on Wed, Jan 10, 2007 at 11:25:14AM CET:
> On Tue, 9 Jan 2007, Ralf Wildenhues wrote:

> /bin/bash ./libtool --tag=F77   --mode=link g77  -g -O2   -o fprogram 
> fprogram.o libfoo.la 
> g77 -g -O2 -o fprogram fprogram.o  ./.libs/libfoo.a
> /usr/local/bin/ld: crt1.o: No such file: No such file or directory
> collect2: ld returned 1 exit status

Hmm.  This looks like your g77 installation is a bit broken.
Does it work fine for other uses?  Can you go into the f77demo
directory and issue
  /bin/bash ./libtool --tag=F77 --mode=link g77 -v -g -O2   -o fprogram 
fprogram.o libfoo.la 

to find out where crt1.o should be, and maybe also why it isn't there?
(I'd guess something like
/usr/local/lib/gcc/...sparc.../3.4.6/../../../../lib/crt1.o )

[...]
> FAIL: f77demo-make.test
> === Running f77demo-exec.test
> You must run f77demo-make.test before running ./f77demo-exec.test
> SKIP: f77demo-exec.test
[...]
> The errors about "You must run f77demo-make.test before..." seem
> a bit odd to me, since we have just done that...

Yeah, that's right.  The testsuite can't distinguish the case where the
required test failed or wasn't run at all.  For CVS Libtool, we're
slowly moving to an Autotest-based testsuite...

Cheers,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]