[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: petscvariables: hardwired build dir instead of install dir
- To: petsc-dev@xxxxxxxxxxx
- Subject: Re: petscvariables: hardwired build dir instead of install dir
- From: "Lisandro Dalcin" <dalcinl@xxxxxxxxx>
- Date: Sat, 22 Mar 2008 11:00:07 -0300
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=BrDq7UJAggF3j0eUv9+oXpKq4Bs7+VGExGxoQRrIpiQ=; b=UccWBgfCL1kOh1OqzRWHgbhq9WI6ey5pmnKQZUfvFV6cbLmFAp05YAVmTnRCf5+V+s7Jeuao/ggpiaGkVEqAqoED7yj5mguosSfqusMLE1FfGNeT/pZ3zjyo7C5rxoRboR9W9g6NDHJRnFpC22Du+5IjcpywxneHlkn9VLGeHKU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BVLnrZkRLRztDB/R0zk5dSSvtr/xfBgjVemdzA1k20AIowxdSVKVtat6tKEZCuFuSWpxWLymFNf0urPGZsXsnxtrfNdTw1rLrSTev8oDeN0XxD1pGy+jXEgF29DhyBhzWSkQbqzfA4hap47uhZz+dlGEhpGD3JggcWMratTbgoU=
- In-reply-to: <E4C64E4B-F079-4B96-A108-1F0B3FF09123@mcs.anl.gov>
- References: <e7ba66e40803220628k65c9df67t16d59e3a46c3c53c@mail.gmail.com> <E4C64E4B-F079-4B96-A108-1F0B3FF09123@mcs.anl.gov>
- Reply-to: petsc-dev@xxxxxxxxxxx
- Sender: owner-petsc-dev@xxxxxxxxxxx
On 3/22/08, Barry Smith <bsmith@xxxxxxxxxxx> wrote:
> Do you mean that it lists, for example,
> SUPERLU_DIST_LIB = -Wl,-rpath,/Users/bsmith/Src/petsc-dev/arch-icc-
> superlu_dist/lib -L/Users/bsmith/Src/petsc-dev/arch-icc-superlu_dist/
> lib -lsuperlu_dist_2.2
> instead of
> SUPERLU_DIST_LIB = -Wl,-rpath,$PETSC_DIR/arch-icc-superlu_dist/lib -L
> $PETSC_DIR/arch-icc-superlu_dist/lib -lsuperlu_dist_2.2
>
exactly that, as an example, I've just built petsc-dev, passing as
prefix the following '--prefix=/usr/local/petsc/2.3.3/linux-gnu' (yes,
I still want to have multiconfig installations of petsc in a central
location, so I add the PETSC_ARCH to the prefix)
But the 'petscvariables' file stills says, for example
ML_INCLUDE = -I. -I/usr/local/mpich2/1.0.6/include
-I/usr/local/mpich2/1.0.6/include
-I/repos/hg/petsc/petsc-dev/linux-gnu/include
The last include dir is the directory were I've built PETSc. I would
love to see that include as -I${PETSC_DIR}/${PETSC_ARCH}/include. And
now, if external packages got installed in $PETSC_DIR/$PETSC_ARCH, we
perhaps could just put nothing, as that location is always taken into
accout for PETSc itself.
The real problem: if I remove the build dir, the 'petscvariables'
point to locations that no longer exists, This is dangerous. I already
had trouble in the past with the old 'bmake' based system. Is there a
chance to 'fix' this, or I'm missing something?
--
Lisandro Dalcín
---------------
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594