[Top][All Lists]

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

Re: LT 2.2.6 problem with Absoft compiler on Suse 9.3

From: Ralf Wildenhues
Subject: Re: LT 2.2.6 problem with Absoft compiler on Suse 9.3
Date: Tue, 23 Sep 2008 23:09:59 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Hello Tony, Jeff,

* Jeff Squyres wrote on Tue, Sep 23, 2008 at 01:33:35PM CEST:
> Greetings.  I previously posted about a problem with LT 2.2.4 and the
> Absoft fortran compiler 
> (http://lists.gnu.org/archive/html/bug-libtool/2008-05/msg00046.html); we 
> finally had some more time to followup and get some more
> information.  We upgraded to LT 2.2.6a, but as expected, the problem
> still exists there as well (since we didn't provide any further info
> for fixes to go into 2.2.6).

Well yes, back then I was waiting for another tiny bit of information:
and then forgot to ever ping about it.  That is: you already sent output
  f90 -V file.f90
  f90 -v file.f90

but not of
  f90 -V

And yes, this is important to know.  Also while we're at it please of
  f90 -v

(both output and exit status).  Thanks.

> One thing that jumps out at me is the following from the libtool diff:
> 8922c8921
> < with_gcc=no
> ---
>> with_gcc=yes
> Could that be significant?  (I did not examine the configure stdout/
> config.log's closely)

Yes, that is probably the key bit.  But if libtool is changed to just
detect Absoft right, then the tests can be made more robust against
independent changes (otherwise Absoft is at the whim of whether it
matches whatever is good for GCC or not).


reply via email to

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