Re: Wierd PETSc build behavior...

2001-03-01 Thread Adam C Powell IV
Julian Gilbey wrote: > I asked about the wrong variable. The -L{MPI_HOME} seems to be > expanded from one of the following three: ${EXTERNAL_LIB} > ${LAPACK_LIB} ${BLAS_LIB}. What are their definitions? Can you run > make with lots and lots of debugging? Can you search all of your > makefiles

Re: Wierd PETSc build behavior...

2001-03-01 Thread Adam C Powell IV
Julian Gilbey wrote: > I asked about the wrong variable. The -L{MPI_HOME} seems to be > expanded from one of the following three: ${EXTERNAL_LIB} > ${LAPACK_LIB} ${BLAS_LIB}. What are their definitions? Can you run > make with lots and lots of debugging? Can you search all of your > makefiles

Re: Wierd PETSc build behavior...

2001-02-28 Thread Steve Langasek
On Wed, 28 Feb 2001, Adam C Powell IV wrote: > > but it looks like what you need to do here > > is reference another makefile variable called MPI_HOME. > Yup. > > The way to this is > > with the syntax $(MPI_HOME) -- note the parens in place of braces. I > > believe > > ${MPI_HOME} references

Re: Wierd PETSc build behavior...

2001-02-28 Thread Julian Gilbey
On Wed, Feb 28, 2001 at 06:04:42PM -0500, Adam C Powell IV wrote: > I see. So something has changed recently in unstable such that braces don't > always work > any more? I usually use parentheses myself, but upstream has braces all over > the place- > I assumed they were interchangable (okay, s

Re: Wierd PETSc build behavior...

2001-02-28 Thread Julian Gilbey
On Tue, Feb 27, 2001 at 09:11:08PM -0500, Adam C Powell IV wrote: > PETSC_SYS_LIB = -L${LDIR} -lpetsc \ > ${EXTERNAL_LIB} ${LAPACK_LIB} ${BLAS_LIB} \ > ${MPI_LIB} ${SYS_LIB} > [snip] > PETSC_LIB = -L${LDIR} -lpetscts -lpetscsnes -lpetscsles -lpetscdm > -lpetsc

Re: Wierd PETSc build behavior...

2001-02-28 Thread Adam C Powell IV
Steve Langasek wrote: > Hi Adam, > > On Tue, 27 Feb 2001, Adam C Powell IV wrote: > > > > Have you copied the -L option verbatim? If so, the error is clear: > > > there's no $ between the -L and the {. Otherwise, I have no idea. > > > I'm sorry, I was very imprecise. Here are the details: > > >

Re: Wierd PETSc build behavior...

2001-02-28 Thread Adam C Powell IV
Julian Gilbey wrote: > On Tue, Feb 27, 2001 at 09:11:08PM -0500, Adam C Powell IV wrote: > > [snip] > > PETSC_LIB = -L${LDIR} -lpetscts -lpetscsnes -lpetscsles -lpetscdm > > -lpetscmat \ > > -lpetscvec ${PETSC_SYS_LIB} > > [snip] > > Where's the definition of LDIR? That's defined in bmake/c

Re: Wierd PETSc build behavior...

2001-02-28 Thread Adam C Powell IV
Junichi Uekawa wrote: > In Tue, 27 Feb 2001 16:32:38 -0500 Adam cum veritate scripsit : > > > The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... > > As far as I know, mpich used to install itself to $MPI_HOME/build in > versions up to 1.1.2 (the version found in potato), which has

Re: Wierd PETSc build behavior...

2001-02-28 Thread Steve Langasek
On Wed, 28 Feb 2001, Adam C Powell IV wrote: > > but it looks like what you need to do here > > is reference another makefile variable called MPI_HOME. > Yup. > > The way to this is > > with the syntax $(MPI_HOME) -- note the parens in place of braces. I believe > > ${MPI_HOME} references a no

Re: Wierd PETSc build behavior...

2001-02-28 Thread Julian Gilbey
On Wed, Feb 28, 2001 at 06:04:42PM -0500, Adam C Powell IV wrote: > I see. So something has changed recently in unstable such that braces don't always >work > any more? I usually use parentheses myself, but upstream has braces all over the >place- > I assumed they were interchangable (okay, so

Re: Wierd PETSc build behavior...

2001-02-28 Thread Julian Gilbey
On Tue, Feb 27, 2001 at 09:11:08PM -0500, Adam C Powell IV wrote: > PETSC_SYS_LIB = -L${LDIR} -lpetsc \ > ${EXTERNAL_LIB} ${LAPACK_LIB} ${BLAS_LIB} \ > ${MPI_LIB} ${SYS_LIB} > [snip] > PETSC_LIB = -L${LDIR} -lpetscts -lpetscsnes -lpetscsles -lpetscdm -lpetscma

Re: Wierd PETSc build behavior...

2001-02-28 Thread Adam C Powell IV
Steve Langasek wrote: > Hi Adam, > > On Tue, 27 Feb 2001, Adam C Powell IV wrote: > > > > Have you copied the -L option verbatim? If so, the error is clear: > > > there's no $ between the -L and the {. Otherwise, I have no idea. > > > I'm sorry, I was very imprecise. Here are the details: > >

Re: Wierd PETSc build behavior...

2001-02-28 Thread Adam C Powell IV
Julian Gilbey wrote: > On Tue, Feb 27, 2001 at 09:11:08PM -0500, Adam C Powell IV wrote: > > [snip] > > PETSC_LIB = -L${LDIR} -lpetscts -lpetscsnes -lpetscsles -lpetscdm -lpetscmat \ > > -lpetscvec ${PETSC_SYS_LIB} > > [snip] > > Where's the definition of LDIR? That's defined in bmake/commo

Re: Wierd PETSc build behavior...

2001-02-28 Thread Adam C Powell IV
Junichi Uekawa wrote: > In Tue, 27 Feb 2001 16:32:38 -0500 Adam cum veritate scripsit : > > > The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... > > As far as I know, mpich used to install itself to $MPI_HOME/build in > versions up to 1.1.2 (the version found in potato), which ha

Re: Wierd PETSc build behavior...

2001-02-28 Thread Julian Gilbey
On Tue, Feb 27, 2001 at 09:11:08PM -0500, Adam C Powell IV wrote: > [snip] > PETSC_LIB = -L${LDIR} -lpetscts -lpetscsnes -lpetscsles -lpetscdm > -lpetscmat \ > -lpetscvec ${PETSC_SYS_LIB} > [snip] Where's the definition of LDIR? Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: Wierd PETSc build behavior...

2001-02-28 Thread Junichi Uekawa
In Tue, 27 Feb 2001 16:32:38 -0500 Adam cum veritate scripsit : Hello, > I'm having the darndest time figuring out what's going wrong with the > PETSc > build. It was fine when I built and uploaded PPC packages three weeks > ago, > and alpha, sparc and arm seemed to build fine, but it breaks now

Re: Wierd PETSc build behavior...

2001-02-28 Thread Julian Gilbey
On Tue, Feb 27, 2001 at 09:11:08PM -0500, Adam C Powell IV wrote: > [snip] > PETSC_LIB = -L${LDIR} -lpetscts -lpetscsnes -lpetscsles -lpetscdm -lpetscmat \ > -lpetscvec ${PETSC_SYS_LIB} > [snip] Where's the definition of LDIR? Julian -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Re: Wierd PETSc build behavior...

2001-02-28 Thread Junichi Uekawa
In Tue, 27 Feb 2001 16:32:38 -0500 Adam cum veritate scripsit : Hello, > I'm having the darndest time figuring out what's going wrong with the > PETSc > build. It was fine when I built and uploaded PPC packages three weeks > ago, > and alpha, sparc and arm seemed to build fine, but it breaks no

Re: Wierd PETSc build behavior...

2001-02-27 Thread Steve Langasek
Hi Adam, On Tue, 27 Feb 2001, Adam C Powell IV wrote: > > Have you copied the -L option verbatim? If so, the error is clear: > > there's no $ between the -L and the {. Otherwise, I have no idea. > I'm sorry, I was very imprecise. Here are the details: > # For mpich: (woody mpich uses /usr/li

Re: Wierd PETSc build behavior...

2001-02-27 Thread Adam C Powell IV
Julian Gilbey wrote: > On Tue, Feb 27, 2001 at 04:32:38PM -0500, Adam C Powell IV wrote: > > The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... like > > it's > > substituting ${MPI_HOME} with {MPI_HOME} instead of the value of the > > Have you copied the -L option verbatim? If s

Re: Wierd PETSc build behavior...

2001-02-27 Thread Steve Langasek
Hi Adam, On Tue, 27 Feb 2001, Adam C Powell IV wrote: > > Have you copied the -L option verbatim? If so, the error is clear: > > there's no $ between the -L and the {. Otherwise, I have no idea. > I'm sorry, I was very imprecise. Here are the details: > # For mpich: (woody mpich uses /usr/l

Re: Wierd PETSc build behavior...

2001-02-27 Thread Julian Gilbey
On Tue, Feb 27, 2001 at 04:32:38PM -0500, Adam C Powell IV wrote: > The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... like it's > substituting ${MPI_HOME} with {MPI_HOME} instead of the value of the Have you copied the -L option verbatim? If so, the error is clear: there's no $

Re: Wierd PETSc build behavior...

2001-02-27 Thread Adam C Powell IV
Julian Gilbey wrote: > On Tue, Feb 27, 2001 at 04:32:38PM -0500, Adam C Powell IV wrote: > > The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... like it's > > substituting ${MPI_HOME} with {MPI_HOME} instead of the value of the > > Have you copied the -L option verbatim? If so, t

Re: Wierd PETSc build behavior...

2001-02-27 Thread Julian Gilbey
On Tue, Feb 27, 2001 at 04:32:38PM -0500, Adam C Powell IV wrote: > The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... like it's > substituting ${MPI_HOME} with {MPI_HOME} instead of the value of the Have you copied the -L option verbatim? If so, the error is clear: there's no $