From: KIRK, BENJAMIN (JSC-EG) (NASA) <benjamin.kirk-1@na...> - 2004-02-06 15:35:14
This is gonna be ugly, but post the contents of 'make echo' and let me see
what all the compiler flags are... My guess is there is an empty '-I'
before the sfcurves include path. This would be caused, perhaps, by
misconfiguration: maybe configure enabled an option but did not properly set
the include path... If that's the case then I would classify it as a
libmesh issue... :-)
[mailto:libmesh-users-admin@...] On Behalf Of Kevin
Sent: Friday, February 06, 2004 9:24 AM
Subject: [Libmesh-users] Odd compiling problem with libmesh 0.4.1
I am trying to install libmesh at home and I am having
a problem that has me befuddled. I tried many times
but the basic:
should work, I think. I have PETSC installed in /usr/local/petsc-2.1.6 and
PETSC_DIR is set as is PETSC_ARCH=linux-gnu. I use gentoo linux and gcc is
"make" chugs along without issue until:
Compiling C++ (in optimized mode) src/mesh/mesh.C...
src/mesh/mesh.C:35:22: sfcurves.h: No such file or
make: *** [src/mesh/mesh.i686-pc-linux-gnu.o] Error 1
The odd thing is that the actual compile command has
cmp.c hilbert.c Makefile morton.c README
Finally, when I copy sfcurves.h to src/mesh, it
proceeds past mesh.C without problems.
Has anyone experience such oddness? I know it is not
a libmesh issue but it is very strange. Incidentally,
I tried it on a linux box at work (RH9) and exactly
the same thing happened.
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration See the
breadth of Eclipse activity. February 3-5 in Anaheim, CA.
Libmesh-users mailing list
Get latest updates about Open Source Projects, Conferences and News.