[Trilinos-Users] amesos_amd_internal.h

[Thornquist, Heidi K]

Hi Jason,

These errors look like you are not including the path to AMD in your compile/link line.  The AMD code that is in the Trilinos Amesos package is specifically for building KLU, which also requires AMD, not for use with UMFPACK.  It should not be necessary to modify the Amesos_Umfpack.cpp file if the path to the AMD headers used to build the UMFPACK library are correct.  Your link line should also include "-L<path/to/umfpack_and_amd> -lumfpack -lamd".

Please check this and let me know if you continue to have issues.

Thanks,
Heidi

---
Heidi K. Thornquist
Senior Member of Technical Staff
Electrical & Microsystem Modeling
Sandia National Laboratories
P.O. Box 5800, MS 0316
Albuquerque, NM  87185-0316
Phone: (505)284-8426
Fax:   (505)284-5451




On 5/28/09 2:28 PM, "Jason Slemons" <slemons at cray.com> wrote:

Hello,

In packages/amesos/src/Amesos_Umfpack.cpp there is a call to amd_defaults, which I have learned is not related to the chip company but it means approximate minimum degree. I cannot find a definition for amd_defaults though I have found one for AMD_defaults in amesos_amd_internal.h. Should the instances of amd_defaults be replaced with AMD_defaults?

An example of the error I get when compiling a program that calls amd_defis:
/ptmp/slemons/chrislib/libamesos.a(Amesos_Umfpack.o): In function `Amesos_Umfpac                     k::Amesos_Umfpack(Epetra_LinearProblem const&)':
Amesos_Umfpack.cpp:(.text+0x3fe): undefined reference to `amd_defaults'

Im also getting something that seems related in another library.
/ptmp/slemons/christof.trilinos-9.0.3/gccBUILD/lib/libumfpack.a(umf_i_free.o): In function `umf_i_free':
umf_free.c:(.text+0xb): undefined reference to `amd_free'

-Jason


From: James Willenbring [mailto:jmwille at sandia.gov]
Sent: Tuesday, May 26, 2009 6:37 AM
To: Jason Slemons
Subject: RE: cpp examples of zoltan

Jason,

There is no manual that I am aware of that describes this kind of thing.  You will want to delete CPP from DIST_SUBDIRS and SUBDIRS.  DIST_SUBDIRS probably isn't necessary, unless it happens to be defined as $(SUBDIRS), but it doesn't hurt to remove it there too in your case.

If you didn't already know, we will be scrapping the whole build system with our next release, which is due out by Oct 1.

Jim


From: Jason Slemons [mailto:slemons at cray.com]
Sent: Friday, May 22, 2009 5:05 PM
To: Willenbring, James M
Subject: RE: cpp examples of zoltan

Thanks Jim,

When I first read your note about editing the makefile I was scared to touch it but I think I see what you mean and now I think the modification (deleting CPP under DIST_SUBDIRS) should do it. The more I learn about these makefiles the better off ill be. There isn't like a secret developers manual that describes the make process in more detail is there?

Thanks,

-Jason


From: Willenbring, James M [mailto:jmwille at sandia.gov]
Sent: Friday, May 22, 2009 1:36 PM
To: Jason Slemons
Subject: RE: cpp examples of zoltan


Jason,



Unfortunately there is not a very reliable way to reconfigure a subset of Trilinos.  If you really want to avoid reconfiguring, you could edit the Makefile directly to exclude the broken directories from SUBDIRS in the directory above the one you want to skip.  I would also add the option Karen suggested to your list of configure arguments so that if you configure again, you don't end up overwriting the SUBDIRS hack.



In general, I don't advise reconfiguring Trilinos without blowing away your biuld tree and starting from scratch.  Autoconf just don't handle reconfiguring well in general.



When we move to CMake with the next release, your ability to reconfigure will improve in many circumstances (although it will not be possible to configure individual packages from the package level at all).



Jim



________________________________

From: Jason Slemons [slemons at cray.com]
Sent: Friday, May 22, 2009 2:25 PM
To: Willenbring, James M
Subject: cpp examples of zoltan

Hey Jim,

I noticed that the zoltan examples in CPP do not build correctly. I emailed zoltan users and Karen Devine wrote me back saying she and the zoltan team were working on it. Is there some way to tell 'make tests' not to build the c++ examples when I type 'make tests' from my build directory? I was told that  re-running configure with --disable-zoltan-cppdriver added will make this happen, but I wonder if there is some way to re run configure just on zoltan, and not for every package built. When I went to the zoltan directory(BUILD/packages/zoltan) and typed in my configure script it started going through all the packages.

-Jason



-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://software.sandia.gov/pipermail/trilinos-users/attachments/20090528/1bd251e1/attachment-0001.html