>   prophecy$ $GCC_HOME/bin/g++ -o ex9 ex9.C ...
> 
> gives me the same runtime error.
> 
> thanks,
> df 

So there are a few ways to get dynamic libraries to map properly, which
seems to be what is not happening correctly here.  One way, as you are doing
now, is use the linker to add the search path to the executable with the
-Wl,-rpath,.. approach as you are doing now.

Another way is using the LD_LIBRARY_PATH environment variable.

What if you do 

$ export LD_LIBRARY_PATH=$GCC_HOME/lib64:$LD_LIBRARY_PATH
$ g++ -o ex9 ex9.C ...


If at all possible, we try to avoid figuring out which compiler library
search paths are needed -- that is the compiler's job in my view.

Let me know if this approach works for you.  If not I've got one more thing,
but it involves a Makefile change I'm not sure is necessary.

-Ben


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to