See there.
https://gmplib.org/devel/repo-usage.html
On Tue, Aug 29, 2017 at 08:06:30AM -0400, Dennis Clarke wrote:
> Is it standard? Sometimes yes and sometimes no. Depends on the system.
> At least for software that can not be built inside a clean room scenario
> where you have nothing but a
[ apologies in advance .. another long long email from Dennis ]
On 8/29/17 3:18 AM, Emmanuel Thomé wrote:
On Mon, Aug 28, 2017 at 01:28:33PM -0400, Dennis Clarke wrote:
ppc64$ ./configure ABI=mode64 --enable-cxx --prefix=/usr/local \
--libdir=/usr/local/lib
On Mon, Aug 28, 2017 at 01:28:33PM -0400, Dennis Clarke wrote:
> ppc64$ ./configure ABI=mode64 --enable-cxx --prefix=/usr/local \
> > --libdir=/usr/local/lib --build=powerpc970-unknown-linux-gnu
[...]
> checking compiler gcc -m64 -O2 -Wl,-rpath=/usr/local/lib -mcpu=970 -maltivec
> -mfull-toc
On 2017-08-28 23:33:03 +0200, Niels Möller wrote:
> Vincent Lefevre writes:
> > This only works if the user is root. If a non-root user wants to
> > install libraries in his home directory, the right solution is to
> > use LD_LIBRARY_PATH (since GCC doesn't use a run path by
On 8/28/17 5:33 PM, Niels Möller wrote:
Vincent Lefevre writes:
This only works if the user is root. If a non-root user wants to
install libraries in his home directory, the right solution is to
use LD_LIBRARY_PATH (since GCC doesn't use a run path by default).
I never
Vincent Lefevre writes:
> This only works if the user is root. If a non-root user wants to
> install libraries in his home directory, the right solution is to
> use LD_LIBRARY_PATH (since GCC doesn't use a run path by default).
You'd either use LD_LIBRARY_PATH, which is
On 2017-08-28 22:50:23 +0200, Niels Möller wrote:
> Dennis Clarke writes:
>
> > In some manner the pre-existing libs were getting in the way likely
> > because LD_LIBRARY_PATH=/usr/local/lib and thus the new libs in the
> > build_dir/.libs were not used.
>
>
Dennis Clarke writes:
> In some manner the pre-existing libs were getting in the way likely
> because LD_LIBRARY_PATH=/usr/local/lib and thus the new libs in the
> build_dir/.libs were not used.
LD_LIBRARY_PATH tends to override anything else. Don't use that for
anything