Blast - wish I could remember, but I did see that once before and now can't
remember the fix. I can build non-tarballs just fine on my Mac, though, so
it could be a problem with the tarball not picking something up.



On Thu, May 14, 2009 at 12:41 PM, Bryan Lally <la...@lanl.gov> wrote:

> Argh.  This time with attachment attached ...
>
>
> Bryan Lally wrote:
>
>> While we're talking about build failures ...
>>
>> I haven't been able to build any of the 1.3.x releases on my OS X
>> machines.  OS X 10.5.6 (Leopard) on Intel macs.  Attached is the configure
>> command and the failure from last night's development tarball,
>> openmpi-1.3.3a1r21223.tar.gz.  1.2.x builds fine.
>>
>>    - Bryan
>>
>
>
> --
> Bryan Lally, la...@lanl.gov
> 505.667.9954
> CCS-2
> Los Alamos National Laboratory
> Los Alamos, New Mexico
>
> ./configure                                \
>    --prefix=/usr/local/openmpi-1.3.3x     \
>    --disable-mpi-f77                      \
>    --disable-mpi-f90                      \
>    --disable-mpi-profile
>
> make
>
> ...
>
> Making all in tools/orte-iof
> /bin/sh ../../../libtool --tag=CC   --mode=link gcc  -O3 -DNDEBUG
> -finline-functions -fno-strict-aliasing  -fvisibility=hidden
>  -export-dynamic   -o orte-iof orte-iof.o ../../../orte/libopen-rte.la-lutil
> libtool: link: gcc -O3 -DNDEBUG -finline-functions -fno-strict-aliasing
> -fvisibility=hidden -o orte-iof orte-iof.o
>  ../../../orte/.libs/libopen-rte.a
> /Users/lally/Software/openmpi-1.3.3a1r21223/opal/.libs/libopen-pal.a -lutil
> Undefined symbols:
>  "_orte_iof", referenced from:
>      _orte_iof$non_lazy_ptr in orte-iof.o
>  "_orte_routed", referenced from:
>      _orte_routed$non_lazy_ptr in libopen-rte.a(hnp_contact.o)
>      _orte_routed$non_lazy_ptr in libopen-rte.a(rml_base_contact.o)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> make[2]: *** [orte-iof] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive] Error 1
>
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
>

Reply via email to