Re: Tru64 Fortran compiler support (was: FYI: ksh bug on Tru64 UNIX causes current libtool failure)

[Nicolas Joly]

On Thu, Oct 06, 2005 at 06:27:32PM +0200, Ralf Wildenhues wrote:
> Hi Nicolas,
> 
> * Nicolas Joly wrote on Thu, Oct 06, 2005 at 03:00:51PM CEST:
> > On Thu, Oct 06, 2005 at 02:27:26PM +0200, Ralf Wildenhues wrote:
> > > * Nicolas Joly wrote on Wed, Oct 05, 2005 at 03:22:10PM CEST:
> > > > 
> > > > Got 3 failures; log attached.
[...]
> > > This suggests that it should be possible to write archive_cmds (and
> > > possibly archive_expsyms_cmds) in libltdl/m4/libtool.m4:_LT_LINKER_SHLIBS
> > > like a mixture of the $GCC and the non-$GCC case, using $cc_basename and
> > > $GCC as decision criteria.  Would you be willing to work on this?
> > 
> > I'll try, even if i'm not a fortran programmer myself.
> > 
> > > Should I create a preliminary patch you could test?
> > 
> > Yes, please.
> 
> See below.  If all the C compiler does is pass `-expect_unresolved pattern'
> through to the linker anyway, we could also just skip the `case' thingy
> and add the `${wl}' every time..

I just checked that both `-expect_unresolved \*' and
`-Wl,-expect_unresolved -Wl,\*' give the same ld(1) command line.

With your patch the 2 fortran tests now pass :

  9: F77 convenience archives                      ok
 10: FC convenience archives                       ok

And the testsuite looks good :

29 tests behaved as expected.
1 test was skipped.

To summarize, libtool HEAD now works on Tru64 with `BIN_SH=xpg4' set
in the environement.

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.