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 sa
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 (that
On Aug 4, 2009, at 5:50 PM, Jeff Squyres (jsquyres) wrote:
Ah -- I see an AC 2.63b release note:
** AC_REQUIRE now detects the case of an outer macro which first
expands
then later indirectly requires the same inner macro. Previously,
Yes, this is exactly what was happening.
The AC
Ah -- I see an AC 2.63b release note:
** AC_REQUIRE now detects the case of an outer macro which first expands
then later indirectly requires the same inner macro. Previously,
this case led to silent out-of-order expansion (bug present since
2.50); it now issues a syntax warning, and du
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 with
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 b
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
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 back to 2.63 until we figure out a way to solve
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 b
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: AC_LANG_
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
13 matches
Mail list logo
