Bugzilla Bug 146512

I think the by-hand libtool run in the ebuild is broken, the --tag=F77 always
runs g77.

Hmm, I think libtool uses whatever is defined in /usr/bin/libtool under 

# ### BEGIN LIBTOOL TAG CONFIG: F77

which is i686-pc-linux-gnu-gfortran in my case and linking with
--tag=F77 works fine. Have you tried re-emerging libtool with
gcc-4.1.1 to see if it picks up gfortran? Kind of annoying though
for people who switch back and forth between gcc-3 and gcc-4.

Markus

Yes, I have g77 in there instead of gfortran. Presumably a remerge would change
this, but I also would prefer if it were unnecessary.

When I autotooled the *-reference ebuilds, things just worked. Maybe a
mini-autotooling here could work.

I had another look and I think the solution is very simple. We're already
using the autotooled lapack, hence instead of calling /usr/bin/libtool we
just use the one in ${WORKDIR}/LAPACK which amounts to replacing
libtool by ../libtool.

This seems to work for me. I'll commit the change tomorrow unless I discover
any breakage.

Markus

Using the autotooled libtool from lapack-reference works fine for 
me and I've committed the changes to cvs.

Best,
Markus