On May 10, 2006, at 4:09 PM, Ralf Wildenhues wrote:
> * Didier Lucor wrote on Wed, May 10, 2006 at 03:50:45PM CEST:
>>
>> For some reason, I've not received your email (maybe I'm doing
>> something wrong here with the mailing list?)
>
> I have no idea. I've Cc:ed you now.
>
>> This is what I've got:
>>
>>> mpic++ -v -o comm_get_name_cxx comm_get_name_cxx.o -L../reporting -
>> llamtest
>
> Ouch. I meant
> mpic++ -showme -o ...
>
This is what I get this time:
> mpic++ -showme -o comm_get_name_cxx comm_get_name_cxx.o -L../
reporting -llamtest
g++ -I/usr/local/include -D_REENTRANT -o comm_get_name_cxx
comm_get_name_cxx.o -L../reporting -llamtest -Wl,-u -
Wl,_lam_darwin_malloc_linker_hack -Wl,-multiply_defined,suppress -Wl,-
force_flat_namespace -Wl,-flat_namespace -Wl,-multiply_defined -
Wl,suppress -L/usr/local/lib -llammpio -llammpi++ -lmpi -llam -ldl
> Sorry about that.
>
> I have a vague feeling that it's due to an old Autoconf bug[1]
> lingering
> somewhere, but I can't see where Fortran would come into play here.
> Another reason to get Autoconf-2.60 out the door soon, luckily that
> seems pretty near now.
>
> Cheers,
> Ralf
>
> [1] http://lists.gnu.org/archive/html/autoconf-patches/2004-02/
> msg00010.html
|
