On Thu, Aug 20, 2015 at 1:14 PM, Jeff Squyres (jsquyres) wrote:
>
> > And therefore it didn't generate libmpi_mpifh_sizeof.a (gfortran will generate an effectively "empty" libmpi_mpifh_sizeof.a). Hence, a
> subsequent link that depended on that library failed.
>
> Paul: can you verify my theory?
$#%@%@#$%
WTF?
Yes. Somehow I stomped on my $HOME/.gitconfig. :-(
> On Aug 20, 2015, at 4:10 PM, Dave Goodell (dgoodell)
> wrote:
>
> On Aug 20, 2015, at 3:03 PM, git...@crest.iu.edu wrote:
>
>> This is an automated email from the git hooks/post-receive script. It was
>> generated because
On Aug 20, 2015, at 3:56 PM, Jeff Squyres (jsquyres) wrote:
>
>> I'll bet that OMPI determined that your Fortran compiler didn't support
>> enough Fortran mojo to properly support MPI_SIZEOF. So it generated an
>> empty .f90 file. And therefore it
>
> And therefore it didn't generate libmpi
On Aug 20, 2015, at 3:03 PM, git...@crest.iu.edu wrote:
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "open-mpi/ompi".
>
> The branch, master has been updated
> via d5763a82
On Aug 20, 2015, at 3:54 PM, Jeff Squyres (jsquyres) wrote:
>
> Ah, I see the issue:
>
> -
> GENERATE psizeof_f.f90
> FC psizeof_f.lo
> WARNING: Source file "psizeof_f.f90" contains no Fortran statements.
>
> f90comp: 29 SOURCE LINES
> f90comp: 0 ERRORS, 1 WARNINGS, 0 OTHER MESSAGES
Ah, I see the issue:
-
GENERATE psizeof_f.f90
FC psizeof_f.lo
WARNING: Source file "psizeof_f.f90" contains no Fortran statements.
f90comp: 29 SOURCE LINES
f90comp: 0 ERRORS, 1 WARNINGS, 0 OTHER MESSAGES, 0 ANSI
-
As you can see, (p)sizeof_f.f90 is a generated file. I'll bet t
Jeff,
My testing scripts always pass V=1 to each make command, but as you can see
in my report that didn't give full command lines.
It is worth noting that on this system "make" is not Gnu-Make.
I am venturing a guess that this is why V=1 is not producing the expected
output.
That might be the kno
No problem. I should have caught it in my post-cherry-pick tests. I
forgot to test with -m32.
-Nathan
On Thu, Aug 20, 2015 at 11:37:17AM -0700, Paul Hargrove wrote:
>Excellent. Sorry I let this escape into the 1.8.8 release.
>-Paul
>On Thu, Aug 20, 2015 at 10:29 AM, Jeff Squyres (js
Excellent. Sorry I let this escape into the 1.8.8 release.
-Paul
On Thu, Aug 20, 2015 at 10:29 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> (the fix has been merged in to v1.8 and v1.10 branches)
>
> > On Aug 20, 2015, at 12:18 PM, Nathan Hjelm wrote:
> >
> >
> > I see the problem
OK, I'll see what I can do. I have a conf call in an hour.
So I'll if I don't have your requested output before that, it will be much
later today.
-Paul
On Thu, Aug 20, 2015 at 10:53 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> Paul --
>
> Can you give me more info on this?
>
> Ca
Paul --
Can you give me more info on this?
Can you "make clean all V=1" in the ompi/mpi/fortran/mpif-h directory and send
me the output?
Additionally, can you send the output of "ls -l ompi/mpi/fortran/mpif-h/.libs"
after the make?
> On Aug 14, 2015, at 11:40 PM, Paul Hargrove wrote:
>
> T
Paul sent me some additional info off-list, and I fixed the issue.
PR's filed for v1.10 and v2.x.
> On Aug 19, 2015, at 5:09 PM, Jeff Squyres (jsquyres)
> wrote:
>
> On Aug 19, 2015, at 5:01 PM, Todd Kordenbrock wrote:
>>
>> Jeff,
>>
>> The linker error that Paul posted isn't an OFI MTL sp
(the fix has been merged in to v1.8 and v1.10 branches)
> On Aug 20, 2015, at 12:18 PM, Nathan Hjelm wrote:
>
>
> I see the problem. Both Ralph and I missed an error in the
> cherry-pick. For add_32 in the ia32 atomics we were checking for
> OPAL_GCC_INLINE_ASSEMBLY instead of OMPI_GCC_INLINE_A
I see the problem. Both Ralph and I missed an error in the
cherry-pick. For add_32 in the ia32 atomics we were checking for
OPAL_GCC_INLINE_ASSEMBLY instead of OMPI_GCC_INLINE_ASSEMBLY.
-Nathan
On Thu, Aug 20, 2015 at 03:01:35PM +, Jeff Squyres (jsquyres) wrote:
> Paul --
>
> I see that the
Paul --
I see that there was an ASM change in 1.8.8. At first look, it seems harmless
/ shouldn't have caused this kind of problem.
Nathan is checking into it...
> On Aug 14, 2015, at 9:52 PM, Paul Hargrove wrote:
>
> I have a systems running Solaris 11.1 on x86-64 hardware and 11.2 in an
15 matches
Mail list logo
