new build system

Satish Balay balay at mcs.anl.gov
Wed Jun 13 21:45:58 CDT 2007


gcc's model appears to be more similar to PETSc.

[we had petscconf.h in lib :)]

GCC_DIR=/usr/lib/gcc
GCC_ARCH=i386-redhat-linux
GCC_VER=4.1.1

We have 2 variables and they have 3 :). Because they use wrappers [aka
compilers] no env variable is required to do the switch..

Satish

On Wed, 13 Jun 2007, Barry Smith wrote:

> 
>   What the hey are include files doing inside lib? What a crock.
> 
>    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