Yep -- we discussed this after I committed that fix, and I read up on
the AC docs to see why it worked. I now grok, and have a pending fix
queued up for tonight (just so we don't commit autogen-worthy changes)
that fixes exactly what you're talking about. My patch is almost
exactly the
Hello,
* Jeff Squyres wrote on Tue, Aug 04, 2009 at 11:38:29PM CEST:
> https://svn.open-mpi.org/trac/ompi/changeset/21759 seems to make us
> play well with AC 2.64. To be honest, I'm not sure why this change
> works, but it does.
First off, the warnings 2.64 spit out were about real issues
Indeed, r21759 solves the problem. ompi compile successfully on Mac OS
X with autoconf 2.64.
Thanks,
george.
On Aug 4, 2009, at 17:41 , Jeff Squyres wrote:
On Aug 4, 2009, at 5:37 PM, George Bosilca wrote:
I used 2.64 for about a week on a bunch of machines. I never had
problems
On Aug 4, 2009, at 5:37 PM, George Bosilca wrote:
I used 2.64 for about a week on a bunch of machines. I never had
problems with it before...
After checking it turned out that autoconf 2.64 was freshly installed
on my Mac, so this might be a problem with autoconf 2.64 and MAC OS
X ... I'll go
https://svn.open-mpi.org/trac/ompi/changeset/21759 seems to make us
play well with AC 2.64. To be honest, I'm not sure why this change
works, but it does.
I'm going to ping Ralf W. and see if he's got any insight here...
On Aug 4, 2009, at 5:17 PM, Jeff Squyres (jsquyres) wrote:
Checking this further, my C++ changes were r21755. Updating my SVN
tree to the commit before that (r21754), I see that AC 2.64 on this
tree issues these same warnings, but then configure works and the
build seems to proceed as normal.
Did you try AC 2.64 before today?
If not, I'd advise
Doh. I tested with 2.63. I'll check out 2.64 right now...
On Aug 4, 2009, at 4:37 PM, George Bosilca wrote:
Not completely fixed. With the latest version of autoconf (2.64) I get
a bunch of warnings.
configure.ac:449: warning: AC_REQUIRE: `AC_PROG_CXX' was expanded
before it was required
Not completely fixed. With the latest version of autoconf (2.64) I get
a bunch of warnings.
configure.ac:449: warning: AC_REQUIRE: `AC_PROG_CXX' was expanded
before it was required
../../lib/autoconf/c.m4:671: AC_LANG_COMPILER(C++) is expanded from...
../../lib/autoconf/lang.m4:315:
Should be fixed in https://svn.open-mpi.org/trac/ompi/changeset/
21758. Sorry for the interruption...
On Aug 4, 2009, at 10:24 AM, Jeff Squyres wrote:
Doh!
I committed the "we don't need no stinkin' C++ compiler" changes
this morning after a bunch of testing, but I totally neglected to
Doh!
I committed the "we don't need no stinkin' C++ compiler" changes this
morning after a bunch of testing, but I totally neglected to test the
case *with* a C++ compiler. :-(
So the trunk is borked at the moment; I'm working on a fix...
--
Jeff Squyres
jsquy...@cisco.com
Hi Tim,
the configure script of the vt-integration don't check whether MPI I/O
is disabled, so
the VT's MPI_File_* wrapper functions will be built. A quick solution
for this problem should be
to add the option "--with-contrib-vt-flags=--without-mpi-io" to the
configure script.
I'm working on a
On Di, 2008-01-29 at 02:53 -0500, Aurélien Bouteiller wrote:
> DSO build also fail.
>
> ../../../../../../trunk/ompi/contrib/vt/vt/vtlib/vt_comp_gnu.c:312:5:
> warning: "VT_BFD" is not defined
> ../../../../../../trunk/ompi/contrib/vt/vt/vtlib/vt_comp_gnu.c:312:5:
> warning: "VT_BFD" is not
DSO build also fail.
../../../../../../trunk/ompi/contrib/vt/vt/vtlib/vt_comp_gnu.c:312:5:
warning: "VT_BFD" is not defined
../../../../../../trunk/ompi/contrib/vt/vt/vtlib/vt_comp_gnu.c:312:5:
warning: "VT_BFD" is not defined
/usr/bin/ld: cannot find -lz
collect2: ld returned 1 exit status
Hello,
this problem should be fixed now...
It seems that the symbol '__pos' is not available on every platform.
This isn't a problem, because
it's only used for a debug control message.
Regards,
Matthias
On Mo, 2008-01-28 at 09:41 -0500, Jeff Squyres wrote:
> Doh - this is Solaris on x86? I
Doh - this is Solaris on x86? I think Terry said Solaris/sparc was
tested...
VT guys -- can you check out what's going on?
On Jan 28, 2008, at 9:36 AM, Adrian Knoth wrote:
On Mon, Jan 28, 2008 at 07:26:56AM -0700, Ralph H Castain wrote:
We seem to have a problem on the trunk this
Doh -- sorry about that. r17282 removes the erroneous #if.
On Jan 28, 2008, at 9:26 AM, Ralph H Castain wrote:
We seem to have a problem on the trunk this morning. I am building
on a
platform with the following configuration:
with_threads=no
enable_dlopen=no
enable_pty_support=no
On Mon, Jan 28, 2008 at 07:26:56AM -0700, Ralph H Castain wrote:
> We seem to have a problem on the trunk this morning. I am building on a
There are more errors:
/tmp/ompi/src/ompi/contrib/vt/vt/vtlib/vt_iowrap.c: In function
`fsetpos':
/tmp/ompi/src/ompi/contrib/vt/vt/vtlib/vt_iowrap.c:850:
We seem to have a problem on the trunk this morning. I am building on a
platform with the following configuration:
with_threads=no
enable_dlopen=no
enable_pty_support=no
with_tm=/opt/PBS
LDFLAGS=-L/opt/PBS/lib64
with_openib=/opt/ofed
with_memory_manager=no
enable_mem_debug=yes
18 matches
Mail list logo
