configure: error: Unable to find required library, teuchoscore.

[ab.m...@gmail.com]

Hi All,

I am trying to build a parallel xyce 6.8 on windows Ubuntu (using  wsl). I have successfully build trilinos (12.12) from source as per Sandia recommendations.
When running the xyce configure, the build system, complains that it does not find the teuchoscore library. This library among others has been created by the trilino build in the

expected directory. This problem persists even when the library path is explicitly given via --libdir.

the tail of the configure output is as follows:

.........

..........

checking for getpwuid... yes
checking for gethostname... yes
checking for getdomainname... yes
checking for uname... yes
checking for sysconf... yes
checking for /proc/self/stat... yes
checking mathimf.h usability... no
checking mathimf.h presence... no
checking for mathimf.h... no
checking whether the compiler supports isnan and isinf... yes
checking for library containing MPI_Bcast... -lmpi
checking for amd_valid in -lamd... yes
checking for main in -lteuchoscore... no
configure: error: Unable to find required library, teuchoscore.

the "latest" configure line I tried  is:

../../../d/downloads/Xyce-6.8/configure ARCHDIR=="/mnt/d/xyce/xyce_parallel" --exec-prefix="/mnt/d/xyce/xyce_parallel"  --prefix="/mnt/d/xyce/xyce_parallel"  --libdir="/mnt/d/xyce/xyce_parallel/lib"  --srcdir="/mnt/d/downloads/Xyce-6.8" --enable-mpi

the libraries are in /mnt/d/xyce/xyce_parallel/lib.

Thanks for your help

Abderrezak M.

[xyce-users]

Unfortunately, it is nearly impossible to diagnose configure failures simply from the console output of the configure script.  One must look in the file "config.log" that is produced at the time configure is run to see what the real problem is.

At the stage where configure is looking for teuchoscore, it is trying to compile and link a small test program against that library, and is failing.  Configure reports this as "unable to find required library" but really the error means "unable to find and/or make use of required library."  The reason for the failure will be in config.log.

If you post that file we might be able to take a quick look at it and suggest where things may be going wrong.  While you're at it, you might also post the exact cmake invocation you used to build Trilinos, as this might help us work out what is happening for you if config.log doesn't give the whole picture.

[xyce-users]

Can't be absolutely sure this is the problem, but your configure line for Xyce looks wrong:

ARCHDIR=="/mnt/d/xyce/xyce_parallel"

should be

ARCHDIR="/mnt/d/xyce/xyce_parallel"

It's possible that extra equals sign is breaking things.

The "exec-prefix", "libdir" and "srcdir" options don't impact how configure finds libraries, and could be left off.  "prefix" is used only to identify where "make install" should put the code after it's built.

[Abderrezak Mekkaoui]

Thank you for your reply,
I finaly build it using the following:

../../../d/downloads/Xyce-6.8/configure ARCHDIR="/mnt/d/xyce/xyce_parallel"  \
--srcdir="/mnt/d/downloads/Xyce-6.8" CPPFLAGS="-I/usr/include/suitesparse" \
--enable-mpi CXX=mpiCC F77=mpif77

This is as recommended verbatim (except for the paths).

Regression tests were also performed successfully. The final test message is as follows:

"
......
All Test runs complete - Warning 1 Tests FAILED
                                 0 Tests EXITED WITH ERROR
Total testing time:  15.0m (wall),   675s (user),   399s (system)
"

The only line that did not have a "passed" flag is the following:

LTRA/zero_length_lc_line..........................TIME LIMIT[sh]  (Time:  10s =   0.00cs +   0vs)

I am guessing this is OK?

All in all the process was much easier than I have anticipated (the system being a linux "os" running on windows).
Thank you.
Abderrezak M.

--
You received this message because you are subscribed to the Google Groups "xyce-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xyce-users+...@googlegroups.com.
To post to this group, send email to xyce-...@googlegroups.com.
Visit this group at https://groups.google.com/group/xyce-users.
For more options, visit https://groups.google.com/d/optout.

[xyce-users]

On Monday, July 2, 2018 at 3:33:52 PM UTC-6, Abderrezak Mekkaoui wrote:

Thank you for your reply,
I finaly build it using the following:

../../../d/downloads/Xyce-6.8/configure ARCHDIR="/mnt/d/xyce/xyce_parallel"  \
--srcdir="/mnt/d/downloads/Xyce-6.8" CPPFLAGS="-I/usr/include/suitesparse" \
--enable-mpi CXX=mpiCC F77=mpif77

This is as recommended verbatim (except for the paths).

Glad it was that easy.

Regression tests were also performed successfully. The final test message is as follows:

"
......
All Test runs complete - Warning 1 Tests FAILED
                                 0 Tests EXITED WITH ERROR
Total testing time:  15.0m (wall),   675s (user),   399s (system)
"

The only line that did not have a "passed" flag is the following:

LTRA/zero_length_lc_line..........................TIME LIMIT[sh]  (Time:  10s =   0.00cs +   0vs)

I am guessing this is OK?

I wouldn't go as far as saying it's "OK" but it is not uncommon.  We have found that "mpirun" can randomly hang after Xyce exits, and the "run_xyce_regression" script detects that and kills the hung process after a time limit.  The frequency at which hang this happens varies widely from platform to platform and from MPI version to MPI version.  We've seen it on most platform/MPI combinations to be a "one-in-10-thousand" event, but on others much more frequently than that.  We have not yet found the reason for it, as it is happening after Xyce exits --- somehow mpirun just gets stuck.  The specific test you are seeing fail here is one that should exit very quickly with an error message, and instead it took over 10 seconds to exit.  That test has a 10 second time out.  Most tests have a 30 minute time out.

If you rerun the test suite this same test probably won't fail again, but others might.  When these things hang, Xyce has always finished its work and produced valid output, but the test is flagged as an error because of the hang.

All in all the process was much easier than I have anticipated (the system being a linux "os" running on windows).

We're glad you  are up and running.  Thank you for your interest in Xyce.

The Xyce Team.

To unsubscribe from this group and stop receiving emails from it, send an email to xyce-users+unsubscribe@googlegroups.com.