Re: Missing symbols in LAPACK/PETSc

2002-01-18 Thread Phil Blundell
On Fri, 2002-01-18 at 02:18, Adam C Powell IV wrote: > So that would seem to make for two RC bugs: one against gcc-2.95 for > these LC* mystery symbols in fortran libs, and the other against > gcc-3.0_3.0.3-1 for not building, right? I think I looked at fixing this in 2.95 a long time ago and di

Re: Missing symbols in LAPACK/PETSc

2002-01-17 Thread Adam C Powell IV
Philip Blundell wrote: On Thu, 2002-01-17 at 16:28, Adam C Powell IV wrote: /usr/lib/liblapack.so: undefined reference to `LC13' It's a compiler bug. Try gcc-3.0, and/or file a bug report. [This was while trying to build illuminator.] Okay... Unfortunately, 3.0.3 has never successfully built on

Re: Missing symbols in LAPACK/PETSc

2002-01-17 Thread Philip Blundell
On Thu, 2002-01-17 at 16:28, Adam C Powell IV wrote: > /usr/lib/liblapack.so: undefined reference to `LC13' It's a compiler bug. Try gcc-3.0, and/or file a bug report. p.

Re: Missing symbols in LAPACK/PETSc

2002-01-17 Thread Adam C Powell IV
Othmar Pasteka wrote: hi, On Thu, Jan 17, 2002 at 11:28:50AM -0500, Adam C Powell IV wrote: I'm trying to build illuminator, which is based on PETSc, which in turn uses BLAS and LAPACK. But when I go to link a binary executable against these libs, I get: /usr/lib/liblapack.so: undefined referen

Missing symbols in LAPACK/PETSc

2002-01-17 Thread Adam C Powell IV
Greetings, I'm trying to build illuminator, which is based on PETSc, which in turn uses BLAS and LAPACK. But when I go to link a binary executable against these libs, I get: gcc -g -O2 -o .libs/chts chts.o cahnhill.o -L/usr/lib/petsc/lib/libO/linux -lpetscts -lpetscsnes -lpetscsles -L/usr/li