[petsc-dev] Configure problem on Titan

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:

> On Wed, 11 Mar 2015, Jed Brown wrote:
>
>> Barry Smith <bsmith at mcs.anl.gov> writes:
>> >   If one fails then configure moves on an tries with the other. Is
>> >   this a problem? We do it all over the place on configure.
>> 
>> The problem is that both may "work" (link without errors), but exhibit
>> subtle errors at run-time due to ABI mismatch.
>> 
>
> The current usage mode here is:
>
> --with-clib-autodetect=0 --with-cxxlib-autodetect=0 --with-fortranlib-autodetect=0 LIBS=-lstdc++

Right.  I think this is better, even though it's annoyingly verbose.

> In this mode - I don't think configure should be gussing - and let the
> user provide the appropriate compatibility library list.
>
> If any fixes - they should go for usage:
> --with-clib-autodetect=1 --with-cxxlib-autodetect=1 --with-fortranlib-autodetect=1

Sure, but this is the default and it's better to error at configure time
than to execute incorrectly when run.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150311/fb6de3b6/attachment.sig>