Thanks for the investigation and confirmation!
--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
I haven't populated it with an actual
> graph so there's nothing to send with MPI_Alltoall.
>
>
--
Jeff Squyres
jsquy...@cisco.com
Can you provide a small reproducer of the issue?
#x27;re getting back from lt_dlopen() invalid? All we can tell from this
test is that it's not NULL.
Specifically: I'm not sure that calling lt_dlerror() will return anything
meaningful if there has been no error.
--
Jeff Squyres
jsquy...@cisco.com
eplace...? I'd
be happy to give it a whirl on my side (i.e., on RHEL and/or MacOS) with the
full complement of exactly the (stock) Autotools versions you're using to see
if that triggers the issue.
--
Jeff Squyres
jsquy...@cisco.com
e think that makes a difference?)
Libtool 2.4.6
I am also using gcc 7.3.0.
Here's the directory I built in:
/home/jsquyres/openmpi-releases/build/openmpi-LjweZK/openmpi-3.0.1
I'm *not* running on Debian -- I'm running on an RHEL machine -- but this seems
like a path issue, not a distro issue, so I'm kinda hoping that that doesn't
matter...
Any thoughts?
--
Jeff Squyres
jsquy...@cisco.com
re-tkr-sizeof.h and mpi-ignore-tkr-sizeof.f90), but those are clearly
delineated as dependencies.
Maybe you can put a patch in that Makefile.am that causes libtool to be cat'ed
(or even emailed to yourself -- hah!) so that we can potentially run it
manually / trace it to see where this blank library name is coming from...?
--
Jeff Squyres
jsquy...@cisco.com
coming from.
If we're not able to get the CI build product, has anyone been able to
reproduce the error manually?
--
Jeff Squyres
jsquy...@cisco.com
library names. If those .la files got built
incorrectly somehow, that could lead to link errors later like this...?
Is it possible to check the build product from your automated CI like this?
This is using the Open MPI-bootstrap-provided libtool, right (i.e., from the
Open MPI 3.0.x tarball)? I.e., you didn't invoke "autogen.pl" again to
re-bootstrap the Open MPI build system, right?
--
Jeff Squyres
jsquy...@cisco.com
).
1.7 is a "feature" release. OMPI 1.odd.x series are stable and tested; they're
just not as time-tested out in the real world as OMPI 1.even.x series.
We're anticipating 1.8 will be out in early 2014.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go t
"wontfix" or reference #193 and leave it open with severity
> "wishlist". (But I doubt that someone will implement that soonish.)
The right ticket to reference is probably this one:
https://svn.open-mpi.org/trac/ompi/ticket/1241
--
Jeff Squyres
jsquy...@cisco.com
For corp
ffect, contra the documentation --
>> this perhaps ought to be its own bug. (I can set MCA parameters for R
>> with environment variables, but that's not nearly as convenient as the
>> host file.)
>
> I'm out of ideas here. Jeff, could you please commen
Adding pthread could fix something, but I'm a little dubious. It seems
unlikely.
You should probably contact the Aztec authors at this point.
Sent from my PDA. No type good.
On Sep 3, 2010, at 3:05 AM, Rachel Gordon
wrote:
> Dear Jeff, Ralf and Manuel
>
> There are some good news,
> I a
used in C.
You might want to check the Aztec source code and see if it is doing that
properly, or if it is just using the handle passed from Fortran without
conversion. If so, this would be an Aztec problem -- nothing to do with Open
MPI or Debian (i.e., the MPI standard says you must cal
#x27;t used g77 in years. Is there any reason you're not using
gfortran? I was under the impression (perhaps mistakenly) that gfortran was
the next generation after g77 and g77 was long-since dead...?
> Rachel
>
>
>
>
> On Thu, 2 Sep 2010, Jeff Squyres wrote:
&
] [ 6] sample(main+0x2c) [0x44e8ec]
> [cluster:00377] [ 7] /lib/libc.so.6(__libc_start_main+0xe6) [0x7f6b54cfd1a6]
> [cluster:00377] [ 8] sample [0x407459]
> [cluster:00377] *** End of error message ***
> --
>
&g
can safely extract
the actual flags by using the --showme options. Check out:
http://www.open-mpi.org/faq/?category=mpi-apps#cant-use-wrappers
On Sep 2, 2010, at 7:45 AM, Jeff Squyres (jsquyres) wrote:
> If you're segv'ing in comm size, this usually means you are using the wrong
&
If you're segv'ing in comm size, this usually means you are using the wrong
mpi.h. Ensure you are using ompi's mpi.h so that you get the right values for
all the MPI constants.
Sent from my PDA. No type good.
On Sep 2, 2010, at 7:35 AM, Rachel Gordon
wrote:
> Dear Manuel,
>
> Sorry, it d
lready available here:
https://svn.open-mpi.org/trac/ompi/ticket/2559
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "
I just replied to this issue on the Open MPI user's list:
http://www.open-mpi.org/community/lists/users/2010/07/13714.php
It would be good to know if this is still happening.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/
These patches were accepted into OMPI v1.3.3:
https://svn.open-mpi.org/trac/ompi/changeset/21493
Exact release date is unknown, but hopefully "soon".
On Jun 20, 2009, at 7:23 AM, Jeff Squyres wrote:
Done. The two patches you need are here:
https://svn.open-mpi.org
2009 at 06:52:03AM -0400, Jeff Squyres wrote:
2. If you want a more general env variable name, like checking for
the
presence of $FAKEROOTKEY (or whatever), let me know and we can also
add a
check for that upstream. To be clear, I think I'm going to do #1
anyway
-- it's a nice way f
anyway -- it's a nice way for our users to disable this stuff. But
I'm not opposed to having a fakeroot-specific environment variable
check as well.
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
we
want to use?
Note that this would be a fairly Open MPI-specific environment
variable. This would be fine with me, but I don't know you want a
more generic fakeroot solution in case anyone else ever runs into this
problem...?
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE,
like
"stat()" in the __malloc_initialize_hook(). If that is the accepted
view, then having a way to suppress this behaviour, say with an
environment variable as suggested by Jeff Squyres, seems appropriate.
That would let me solve my problem by setting the variable in
debian/rules. Or
m is a better bet.
Manuel -- can you ping the fakeroot people? It would be preferable to
the method described in that URL.
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
oc_initialize_hook is a bad thing. Perhaps the stat() in
fakeroot caused a memory allocation, whereas the regular stat() does
not, as this code doesn't segfault in normal use.
This is what I had in mind as well.
Thanks for your work so far! I'm quite confident that we can sort it
out
nes in a single mpi job - see faq) and
for debugging.
I'll be back in range in several hours (boarding a floight right now).
-jms
Sent from my PDA. No type good.
- Original Message -
From: Manuel Prinz
To: Steve M. Robbins
Cc: Jeff Squyres (jsquyres); 531...@bugs.debian.org <
On Jun 5, 2009, at 2:39 PM, Jeff Squyres wrote:
FWIW, debugging OMPI is easier if you tell OMPI to slurp all the
plugins into its libraries -- so there's no dlopen's and all the
plugins are physically located in libmpi.so (and friends). You can
get better call stacks thi
#x27;s looking
for the symbol "open"...? I don't know enough about how dlsym works
internally --perhaps that's normal...?
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ese kinds of issues...
FWIW, I'm now leaving for the day -- it's after 6pm here (US Eastern
time). If it would help to jump on the phone tomorrow and explain
this stuff further, let me know. I'm out most of the morning, but
have time available in the afternoon.
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
*same* foo, and therefore only include *one* foo in the resulting
executable.
Make sense?
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I
didn't want you guys prioritizing this because of one whiny guy. I
just wanted to bring it to your attention and let you decide how you
wanted to prioritize it.
That said, I appreciate all the work you've already done on
packaging OpenMPI for Debian and for the time you&
s://svn.open-mpi.org/trac/ompi/changeset/17892
Sorry about that!
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ps://svn.open-mpi.org/svn/ompi/tmp-public/libatomic-ops
Be sure to see our "how to compile OMPI from SVN" page:
http://www.open-mpi.org/svn/building.php
How does this sound?
On Mar 19, 2008, at 9:41 AM, Jeff Squyres wrote:
On Mar 18, 2008, at 12:10 PM, Dirk Eddelbuettel wrote:
age in Open MPI because:
- it doesn't work for all compilers
- it doesn't work for all OS's / platforms
- and therefore it won't be our default/core
Hence, linking to it via an external header / library is fine.
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
great. But it'll require some investigation first.
I should also point out that we're gearing up for branching for the
v1.3 series and are rushing to finish some critical features before
deadline. To be honest and not inflate expectations, I kinda doubt
that we'll have the time t
unk to make them actually function properly; we
decided to give up on the 1.2 branch and focus our efforts on the
v1.3 series (where "we" doesn't actively include me -- others are
doing the threaded work).
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to [EMAIL P
e-progress-threads and --enable-mpi-threads configure
options result in broken-ness on the v1.2 branch; you should not use
them. There is ongoing development work in the trunk to fix the code
associated with these options. The current goal is to have them
working for the v1.3 release.
--
Je
.2/
That way, if there's still a problem, we potentially still have [a
little] time to fix it before 1.2.4.
--
Jeff Squyres
Cisco Systems
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
think of "fixed in experimental").
FWIW, the OMPI subversion trunk has diverged quite a bit from the
v1.2 branch; you might want to wait until the fixes get moved over to
the v1.2 branch and take a snapshot from there (i.e., what will
eventually become the v1.2.4 release).
--
Jef
for Fortran *always* needing the -I).
This fix is too late for the upcoming v1.2, but it will make it in
future releases.
--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
42 matches
Mail list logo
