thank you ben.
I will give that a try.
df
On Sat, 9 Aug 2008, Benjamin Kirk wrote:
>> Maybe something went wrong in my local install?
>> w/ the system gcc there is no problem.
>
> Certainly it seems something is off...
>
> In any case, the other approach I would call more of a hack, but it
> Maybe something went wrong in my local install?
> w/ the system gcc there is no problem.
Certainly it seems something is off...
In any case, the other approach I would call more of a hack, but it will
work...
Edit your Make.common & Make.common.in, and change line 30
>From
libmesh_LDFLAGS
thanks Ben,
this was confusing me. the LD_LIBRARY_PATH is set correctly
> $ export LD_LIBRARY_PATH=$GCC_HOME/lib64:$LD_LIBRARY_PATH
but it only executes if I link with the
> -Wl,-rpath,.. approach
BTW,
I only have this prob w/ my own local install of gcc.
Maybe something went wrong in my lo
> 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 pa
/2008 3:31 PM
> To: [email protected]
> Subject: [Libmesh-users] runtime path
>
> Hi,
>
> when trying to compile code with the "limesh-config" tool
> I am getting runtime linking errors during execution.
>
>
> I have installed my own version of gc
ECTED] on behalf of David Fuentes
Sent: Sat 8/9/2008 3:31 PM
To: [email protected]
Subject: [Libmesh-users] runtime path
Hi,
when trying to compile code with the "limesh-config" tool
I am getting runtime linking errors during execution.
I have installed my own versio
Hi,
when trying to compile code with the "limesh-config" tool
I am getting runtime linking errors during execution.
I have installed my own version of gcc and to get the executable to run,
I need to add the gcc run time path to the compile command.
-Wl,-rpath, $GCC_HOME/lib64
where $GCC_HOME
