FWIW: I'm thinking that this is a bug in Libtool 2.4.3/2.4.4.
See https://github.com/open-mpi/ompi/issues/311#issuecomment-66885102 for more
details.
On Dec 9, 2014, at 11:54 AM, Nick Papior Andersen wrote:
> Yes, I know, but it might give a clue as to what goes wrong in the autogen
> script
Yes, I know, but it might give a clue as to what goes wrong in the autogen
script (as the config path is erroneous), what is peculiar is that it only
happens for that sub-directory, so that should narrow the search down :)
I am glad it worked :)
2014-12-09 16:32 GMT+00:00 George Bosilca :
> Than
Thanks for the hint, it does fixes the problem. But it has to be applied on
the build directory after every configure ...
George.
On Tue, Dec 9, 2014 at 2:27 AM, Nick Papior Andersen
wrote:
> I experience the exact same thing.
> Please see my bug-report on this (and the work-around) here:
>
Yeah, we’ve confirmed at Intel that OMPI won’t build with libtool 2.4.3+
I made Jeff aware of it, but we’re both too busy to dig into this before the
holiday.
> On Dec 8, 2014, at 11:27 PM, Nick Papior Andersen
> wrote:
>
> I experience the exact same thing.
> Please see my bug-report on thi
I experience the exact same thing.
Please see my bug-report on this (and the work-around) here:
http://www.open-mpi.org/community/lists/devel/2014/11/16371.php
2014-12-09 7:57 GMT+01:00 George Bosilca :
> After updating to the latest master (3a14c8e), I start having issues with
> the VPATH build
After updating to the latest master (3a14c8e), I start having issues with the
VPATH build on Mac OS X. The autogen.pl and configure succeeded but when make
is invoked I got the following error:
Making all in opal
Making all in include
/Applications/Xcode.app/Contents/Developer/usr/bin/make all-
