[petsc-dev] CFLAGS and COPTFLAGS

Barry Smith bsmith at mcs.anl.gov
Wed Jan 22 13:16:27 CST 2014

  When we first tried to follow “community standards” with —prefix I was told that “community standards” did not recognize the need for multiple installs and that community standards did not allow for putting archs onto names to allow multiple installs.  We specifically removed the concept of PETSC_ARCH for installs for this reason. Have community standards changed?



On Jan 22, 2014, at 11:31 AM, Jed Brown <jed at jedbrown.org> wrote:

> Sean Farley <sean.michael.farley at gmail.com> writes:
>> jed at jedbrown.org writes:
>>> Sean Farley <sean.michael.farley at gmail.com> writes:
>>>>>  $prefix/bin/petsc-${version}-${arch}-config
>>>>> and symlink $prefix/bin/petsc-config to it by default?
>>>>> Then always namespace libraries and includes?
>>>> This is what I had in mind as well. Though, distributions would remove
>>>> the symlink since that would conflict.
>>> Debian would probably manage it through /etc/alternatives.
>> Just a note that MacPorts would manage it through etc/select :-)
> Thanks, Sean.  (I really was asking you as much as Barry/Matt/Satish/etc.
> Packaging is a different environment.)
> What do the rest of you think?

More information about the petsc-dev mailing list