Hi Roy,
many thanks for your answer. In Attachment you can find the config.log and
make.comon files.
i relized this problem as i checked the make.comon file line 306: there is a
query only for petsc 2.3.x with the path to PETSC_DIR directory with bmake. If
i changed the path after the query in line 306 to the folder, where petsc 3.4.3
was installed, it also didn't work.
Giang
Roy Stogner <[email protected]> schrieb am 21:23 Sonntag, 1.Dezember
2013:
On Sat, 30 Nov 2013, tong giang wrote:
> Make.common:306:
> /home/giang/libmesh/contrib/slepc-3.4.3/bmake/arch-linux2-c-debug/packages:
> no file or directory exists
This is baffling. The references to bmake in our build system should
only be active for PETSc 2.3.x, and they shouldn't be touched unless
that directory exists. We never touch a "packages" file relating to
PETSc. Our longest Make.common file is 192 lines long, so certainly
shouldn't have an error on line 306.
I don't know where we'd even begin diagnosing this without more
information. A copy of your config.log and your 300+ line Make.common
might be helpful. Cc: me on the email in case our mailing list
filters object to the attachments.
---
Roy
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
