| Summary: | lapack-atlas 3.7.15 tries to link with g77 on a gcc-4 system | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Donnie Berkholz (RETIRED) <dberkholz> |
| Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Donnie Berkholz (RETIRED)
2006-09-05 22:33:34 UTC
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 |