Re: ocaml compiled binaries and rpath

2003-04-15 Thread Sven Luther
On Tue, Apr 15, 2003 at 07:02:16PM +0900, Junichi Uekawa wrote: > > > > Just ignore it or add a override. > > > > > > Any reason not to Build-Depend: chrpath, and do 'chrpath --delete' on > > > the result? > > > > Personnaly i don't know, i am no expert in rpath and don't fully > > understand the

Re: ocaml compiled binaries and rpath

2003-04-15 Thread Junichi Uekawa
> > > Just ignore it or add a override. > > > > Any reason not to Build-Depend: chrpath, and do 'chrpath --delete' on > > the result? > > Personnaly i don't know, i am no expert in rpath and don't fully > understand the issues involved. If you are adding an rpath to a non-default directory, the

Re: ocaml compiled binaries and rpath

2003-04-15 Thread Sven Luther
On Mon, Apr 14, 2003 at 05:07:26PM -0600, Joel Baker wrote: > On Fri, Apr 11, 2003 at 11:11:17AM +0200, Sven Luther wrote: > > On Thu, Apr 10, 2003 at 10:56:34PM +0200, Martin Pitt wrote: > > > lintian says: > > > > > > W: planets: binary-or-shlib-defines-rpath ./usr/bin/planets > > > /usr/lib:/us

Re: ocaml compiled binaries and rpath

2003-04-14 Thread Joel Baker
On Fri, Apr 11, 2003 at 11:11:17AM +0200, Sven Luther wrote: > On Thu, Apr 10, 2003 at 10:56:34PM +0200, Martin Pitt wrote: > > lintian says: > > > > W: planets: binary-or-shlib-defines-rpath ./usr/bin/planets > > /usr/lib:/usr/X11R6/lib > > N: > > N: The binary or shared library defines the `RP

Re: ocaml compiled binaries and rpath

2003-04-11 Thread Sven Luther
On Thu, Apr 10, 2003 at 10:56:34PM +0200, Martin Pitt wrote: > Hi! > > I'm just packaging planets (#187988) which is written in ML and > compiled with ocaml. The problem is that the ocaml linker uses the > rpath feature (i. e. hardcoded libary paths). Yes, it does ... > It seems to be against De

Re: ocaml compiled binaries and rpath

2003-04-10 Thread Remi Vanicat
Martin Pitt <[EMAIL PROTECTED]> writes: > Hi! > > I'm just packaging planets (#187988) which is written in ML and > compiled with ocaml. The problem is that the ocaml linker uses the > rpath feature (i. e. hardcoded libary paths). I don't know the answer, but you should ask on debian-ocaml-maint@