If you go at the top of the configure output, basically just after the
detection of the revision, you will see this warning. Somehow, it
doesn't stop configure from working, but it prevent it from doing what
it was supposed to do as the two conditionals are having the wrong
On Oct 22, 2009, at 21:16 , Ralph Castain wrote:
> Most interesting - I have been building on Mac OSX both yesterday
> and today with those changes without problem. I am on Snow Leopard,
> but I checked and "true" is indeed in /usr/bin.
> I'm not seeing any warnings or problems. Perhaps a difference in
> configuration? Though I did also test it with a completely empty ./
> configure --prefix=foo run, again with no problems.
> On Oct 22, 2009, at 7:09 PM, George Bosilca wrote:
>> There seems to be an issue with the latest changes on the configure
>> scripts. A careful reading of the output of configure on MAC OS X
>> shows a lot of errors/warnings, which leads to undefined
>> AM_CONDITIONALS (PROJECT_OMPI_*). This apparently comes from
>> configure.ac line 62 where the path to /bin/true is hardcoded! Of
>> course /bin/true doesn't exist on MAC OS X, instead it is locate
>> in /usr/bin/.
>> checking how to create a ustar tar archive... gnutar
>> ../ompi/configure: line 5480: /bin/true: No such file or directory
>> ../ompi/configure: line 5488: /bin/true: No such file or directory
>> devel mailing list
> devel mailing list