On Sep 15, 2005, at 8:17 PM, Ferris McCormick wrote:
On Thu, 15 Sep 2005, Ferris McCormick wrote:
On Thu, 2005-09-15 at 15:26 -0500, Brian Barrett wrote:
Gah... The #if 0 and missing header are my bad - I'll fix those
tonight. can you rerun the compiler on the file that errors out, but
with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 15 Sep 2005, Ferris McCormick wrote:
On Thu, 2005-09-15 at 15:26 -0500, Brian Barrett wrote:
Gah... The #if 0 and missing header are my bad - I'll fix those
tonight. can you rerun the compiler on the file that errors out, but
with the -S
Jeff and everyone else I contacted about this: thanks for helping track
down the problem. I've been beating my head on this for a few days and
don't have the library experience to have caught these nuances. Thanks
again!
-- Nathan
Correspondence
--
On Sep 15, 2005, at 4:32 PM, Jeff Squyres wrote:
This allows the components themselves to pull in shared libraries when
they are dlopened -- if they need to. If the symbols can be resolved
in the parent process' public symbol namespace, they still will be (as
in the standalone executable exampl
On Thu, 2005-09-15 at 15:26 -0500, Brian Barrett wrote:
> Gah... The #if 0 and missing header are my bad - I'll fix those
> tonight. can you rerun the compiler on the file that errors out, but
> with the -S option to get the assembly file? It would be useful to
> know what is on lines 61,
Followup for the list... a bit of explanation of Nathan's problem about
shared libraries and unresolved symbols.
Short version:
--
It's an OMPI bug when built as a shared library (not an issue for
static libraries). The fix is straightforward, but involves grunt
work. I'll try t
Gah... The #if 0 and missing header are my bad - I'll fix those
tonight. can you rerun the compiler on the file that errors out, but
with the -S option to get the assembly file? It would be useful to
know what is on lines 61, 195, and 292.
Thanks!
Brian
On Sep 15, 2005, at 8:36 AM, Fe
> On Wed, 14 Sep 2005, Brian Barrett wrote:
>
> > I committed some code that should fix the timer problems on SPARC
> > linux. Can you either svn up and try again (or, if you are using
> > nightly builds) try tomorrow's tarball and see if it works? The test
> > tests/util/opal_timer.c should gi
