new build system
Barry Smith
bsmith at mcs.anl.gov
Wed Jun 13 21:39:36 CDT 2007
Sounds like it should be
/usr/include/petsc/2.3.3/opt/*.h
/usr/bin/petsc/2.3.3/opt/petscmpiexec
/usr/lib/petsc/2.3.3/opt/libpetsc.a
/conf/petscrules
Is this correct?
Barry
On Wed, 13 Jun 2007, Satish Balay wrote:
>
>
> On Wed, 13 Jun 2007, Lisandro Dalcin wrote:
>
> > I am using Fedora Core 6, I've installed ATLAS rpm, see the contents:
>
> gcc, python are representative of packages that can have multiple
> version installed simultaneously.
>
> /usr/bin/python2.4
> /usr/include/python2.4/Python.h
> /usr/lib/python2.4/os.py
> /usr/lib/python2.4/config/Makefile
> /usr/lib/python2.4/config/Setup
>
>
> /usr/lib/gcc/i386-redhat-linux/4.1.1/include/float.h
> /usr/lib/gcc/i386-redhat-linux/3.4.6/include/float.h
>
> /usr/lib/gcc/i386-redhat-linux/4.1.1/libgcc.a
> /usr/lib/gcc/i386-redhat-linux/3.4.6/libgcc.a
>
> etc..
>
> One major difference they have [wrt PETSc] is the internals are not
> directly accessed by users. Only the binaries are. So just having
> gcc, gcc34 as 2 binaries is sufficient to distinguish these 2 packages
> [and these wrappers know the internal paths to the correct version of
> libraries]
>
> Satish
>
>
More information about the petsc-dev
mailing list