[PD-dev] zexy: libtool: link: only absolute run-paths are allowed
Hans-Christoph Steiner
hans at at.or.at
Fri Sep 30 19:19:11 CEST 2011
On Fri, 2011-09-30 at 18:17 +0200, IOhannes m zmölnig wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09/30/2011 06:08 PM, Hans-Christoph Steiner wrote:
> >
> > pddev at windowsxp-i386:~$ svn --version
> > svn, version 1.6.1 (r37116)
> > compiled Apr 11 2009, 12:07:06
>
> thanks.
> however, i actually was trying to ask for the svn-revision of externals/
> (which you get by running "svnversion" within this directory), in order
> to be able to check which commits are already in action when the build
> is running.
>
> > Its the same issue as with Gem. So running it from the command line
> > alone without setting any variables, it builds.
>
> another reason to fix it "properly".
>
> > But running in the
> > whole build, where lots of variables like DESTDIR, prefix, etc. are set,
> > it doesn't work.
>
> does "running from the command line" mean:
> $ cd externals && make zexy
> or does it mean
> $ cd externals/zexy && ./autogen.sh && .configure && make
>
> e.g. is the problematic environment within externals/Makefile or within
> the entire build system?
>
> if the latter, do you have any recommendations how to start such a build
> (preferably with only the zexy part, so we don't have to wait for ages)
> in a debugging session?
I found the source of the problem, or at least one step further.
$libpddir is set to $prefix. $prefix is empty on Windows and Mac OS X.
Somehow, libtool wants to do "-rpath $libpddir", so it ends up as
"-rpath ". Windows DLLs don't need the rpath since they are
relocatable.
Still looking for how to solve this tho...
.hc
More information about the Pd-dev
mailing list