[petsc-dev] switch petsc-dev to use --with-shared-libraries by default?
Aron Ahmadia
aron.ahmadia at kaust.edu.sa
Fri Jun 1 13:21:02 CDT 2012
Yep, I was trying to have PETSc build a flapackblas and that was
falling over. I have a pre-built blas/lapack that I should have tried
switching over to.
A
On Fri, Jun 1, 2012 at 9:18 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> I think the problems come from different types of externalpackage
> usages. [for ex: mpi not built shared]. Also we don't explicitly build
> all externalpackages shared - and this can cause grief in some
> cases. [they just get pulled into libpetsc.so]
>
> We had this default for a while and then gaveup. But now that we
> default to --with-single-library=1 - some of those issues don't bite
> us..
>
> Satish
>
> On Fri, 1 Jun 2012, Barry Smith wrote:
>
>>
>> Is it time to change in petsc-dev the default of --with-shared-libraries to true by default? It is a nicer user experience to use shared libraries (much faster link of executable for example).
>>
>> Does it work pretty much everywhere?
>>
>> Barry
>>
>>
>>
>
More information about the petsc-dev
mailing list