bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool error


From: Ralf Wildenhues
Subject: Re: libtool error
Date: Fri, 26 Jan 2007 12:58:15 +0100
User-agent: Mutt/1.5.13 (2007-01-09)

Hello Matthew,

* Matthew Ford wrote on Fri, Jan 26, 2007 at 05:36:09AM CET:
> I am trying to build subversion 1.4.2 and continue to get this libtool
> error.

> cd subversion/mod_dav_svn && /bin/bash
> /ap/d/serena/tt/build/subversion-1.4.2/libtool --tag=CC --silent
> --mode=link gcc  -g -O2  -g -O2 -pthreads  -L/ap/d/serena/tt/build/lib
> -rpath  -avoid-version -module  -o mod_dav_svn.la  activity.lo
> deadprops.lo file_revs.lo liveprops.lo lock.lo log.lo merge.lo
> mod_dav_svn.lo replay.lo repos.lo update.lo util.lo version.lo
> .../../subversion/libsvn_repos/libsvn_repos-1.la
> .../../subversion/libsvn_fs/libsvn_fs-1.la
> .../../subversion/libsvn_delta/libsvn_delta-1.la
> .../../subversion/libsvn_subr/libsvn_subr-1.la -lsocket  -lz
> 
> libtool: link: only absolute run-paths are allowed

The -rpath option to libtool needs as an argument an absolute path.
Please take a look at the Makefile which issued this.  Most likely
it contains something like
   -rpath $(libdir)

or a similarly named macro.  Find out why the macro is empty; it
shouldn't be.  Usually it would be substituted at the end of configure,
by config.status; in the corresponding Makefile.in there'd be a line
  libdir = @libdir@

or so.  The config.log file may contain information about its setting.

Hope that helps.

Cheers,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]