Thanks for your help. I was able to correct the problem by using gcc2.95 to build gcc3.4.6, then rebuilding all the packages.
Matthew Ford 770.752.3643 for Work 770.235.1346 for Cell -----Original Message----- From: Ralf Wildenhues [mailto:[EMAIL PROTECTED] Sent: Friday, January 26, 2007 6:58 AM To: Matthew Ford Cc: bug-libtool@gnu.org Subject: Re: libtool error 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 ----------------------------------------- The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. _______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool