From: Rodrigo Kumpera [mailto:kump...@gmail.com]
The issue is that we don't want to set RPATH to a value in the dynamic linker
path. This is known to cause all sorts of issues. Setting it
to, for example, /opt/lib is fine but /usr/lib is not.
Just to be clear, setting RPATH and RUNPATH
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Andrés G. Aragoneses
It is not if you use fpm (https://github.com/jordansissel/fpm), instead
Huh. That looks like it deserves a closer look. Thanks for the suggestion,
I'll give
On Fri, Mar 7, 2014 at 7:03 AM, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: Rodrigo Kumpera [mailto:kump...@gmail.com]
The issue is that we don't want to set RPATH to a value in the dynamic
linker
path. This is known to cause all sorts of issues. Setting it
On Wed, Mar 5, 2014 at 10:46 PM, Edward Ned Harvey (mono)
edward.harvey.m...@clevertrove.com wrote:
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Edward Ned Harvey (mono)
So ... http://blog.tremily.us/posts/rpath/
On 06/03/14 03:09, Edward Ned Harvey (mono) wrote:
But I have to say, learning to roll your own packages is difficult.
It is not if you use fpm (https://github.com/jordansissel/fpm), instead
of a distro-specific build toolchain, as I recommended in a previous
message (i.e. simple script to
On 04/03/14 17:23, Edward Ned Harvey (mono) wrote:
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Andrés G. Aragoneses
As far as I understand, LD_LIBRARY_PATH is a system setting that mono
doesn't modify.
Thanks for your
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Andrés G. Aragoneses
Right, LD_LIBRARY_PATH may be simply a fallback. But the thing is, you
don't need LD_LIBRARY_PATH when installing libs in standard prefixes
like /usr or
On 05.03.2014 15:31, Edward Ned Harvey (mono) wrote:
It is a safe conclusion to draw, that *whatever* is specified by
--libdir=DIR, the binary should be linked against libraries in that
directory. (If not specified, libdir is derived from
--exec-prefix=EPREFIX, which is derived from
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Robert Jordan
Non-default Mono installations still need LD_LIBRARY_PATH, otherwise
p/invoke of Mono libraries (libgdiplus, libMonoPosixHelper) won't
work because p/invoke is
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Edward Ned Harvey (mono)
So ... http://blog.tremily.us/posts/rpath/
Actually, the answer is right there - Thank you, Trevor and Emily (tremily).
This works perfectly:
export
@lists.ximian.com
Subject: [Mono-dev] Library path bug in Makefile?
I had a problem, and I figured it out, thanks to this page:
http://www.cc.dtu.dk/?page_id=304
I have a system with mono built as follows:
./configure --prefix=/usr/local/mono-3.2.8 make echo echo
Done echo
followed by
sudo
As far as I understand, LD_LIBRARY_PATH is a system setting that mono
doesn't modify. If you want Mono to work out of the box without the need
to adjust LD_LIBRARY_PATH you need to install it in a standard prefix.
Some distributions consider /usr and /usr/local to be standard (note:
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list-
boun...@lists.ximian.com] On Behalf Of Andrés G. Aragoneses
As far as I understand, LD_LIBRARY_PATH is a system setting that mono
doesn't modify.
Thanks for your response - from the link I originally posted
I had a problem, and I figured it out, thanks to this page:
http://www.cc.dtu.dk/?page_id=304
I have a system with mono built as follows:
./configure --prefix=/usr/local/mono-3.2.8 make echo echo Done
echo
followed by
sudo make install echo echo Ok Ok Ok echo
I would expect,
14 matches
Mail list logo
