I had only suggested gfrotran by name because it is available in both
source and binary form from the pkgsrc repo, and is the successor to g95
within the GCC project. I am fine with the "" text.
-Paul
On Tue, Jan 14, 2014 at 5:41 AM, Jeff Squyres (jsquyres) wrote:
> More tweaking -- I don't t
+1
-Paul
On Tue, Jan 14, 2014 at 5:15 AM, Jeff Squyres (jsquyres) wrote:
> On Jan 14, 2014, at 2:44 AM, Paul Hargrove wrote:
>
> > The problem surfaces on i386 too, and use of gfortran seems the best fix.
> > My recommended rewrite:
> >
> > - On NetBSD-6 (at least AMD64 and i386) libtool misi
More tweaking -- I don't think there's an explicit reason to mention gfortran,
is there?
- On NetBSD-6 (at least AMD64 and i386), and possibly on OpenBSD,
libtool misidentifies properties of f95/g95, leading to obscure
compile-time failures if used to build Open MPI. You can work
around th
On Jan 14, 2014, at 2:44 AM, Paul Hargrove wrote:
> The problem surfaces on i386 too, and use of gfortran seems the best fix.
> My recommended rewrite:
>
> - On NetBSD-6 (at least AMD64 and i386) libtool misidentifies properties of
> f95/g95, leading to obscure compile-time failures if used to
FWIW: source inspection of libtool.m4 reveals that the same problem
probably exists with g95 on OpenBSD (same flawed probe logic is used),
though I have no g95 on my OpenBSD systems to confirm or refute this.
G95/f95 should be fine on other systems because {Net,Open}BSD are the only
platforms on w
The new release note reads:
- Building Open MPI on a NetBSD-6 AMD64 system will run into obscure
compile-time failures if f95/g95 is found in the path. You can work
around such problems by removing g95 from your path.
The problem surfaces on i386 too, and use of gfortran seems the best fix.
A release note works for me.
Probably worth a ticket for possible fix in 1.7.5 or 1.9. You can assign
to me as the only one likely to care.
-Paul [Sent from my phone]
On Jan 13, 2014 9:01 AM, "Jeff Squyres (jsquyres)"
wrote:
> Sounds like a release note to me. Thanks for tracking this down!
Sounds like a release note to me. Thanks for tracking this down!
On Jan 11, 2014, at 5:56 PM, Paul Hargrove wrote:
> I have been able to make some progress on understanding the cause of this
> issue.
>
> Looking at the generated libtool is is clearly broken, being for an a.out
> system when
I have been able to make some progress on understanding the cause of this
issue.
Looking at the generated libtool is is clearly broken, being for an a.out
system when this is an elf platform.
Comparison to the WORKING netbsd6-i386 platform revealed the difference is
the presence of g95 on the amd6
Attached is the output from "make install" of 1.7.4rc1 + Jeff's fix for the
symbol conflict on "if_mtu".
There appear to be at least 2 issues.
1) There are lots of (not fatal) messages about ldconfig not existing, but
according to he NetBSD lists that utility went away with the conversion
from a.
10 matches
Mail list logo
