[
https://issues.apache.org/jira/browse/SERF-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Stein resolved SERF-118.
-----------------------------
Resolution: Invalid
Assignee: Greg Stein
Resolving as "invalid". The serf build process builds a static and a shared
library, according to the operating system rules for those libraries. Users of
serf need to use the appropriate mechanisms to link against those libraries.
If there is a problem with the libraries we produce, then that's a bug. But
giving the right rpath to *Subversion* is Not Our Problem.
> scons build not compatible with libtool
> ---------------------------------------
>
> Key: SERF-118
> URL: https://issues.apache.org/jira/browse/SERF-118
> Project: serf
> Issue Type: Bug
> Reporter: Stefan Sperling
> Assignee: Greg Stein
> Labels: Priority-Medium, Type-Defect, scons
>
> *What steps will reproduce the problem?*
> 1. build serf 1.3.0 with scons, using an install prefix that is not in the
> standard library search path
> 2. build Subversion against serf 1.3.0
> Now Subversion binaries cannot run because libserf-1.so cannot be found.
> Adding the $(PREFIX)/serf/lib directory to LD_LIBRARY_PATH works around the
> issue.
> Manually passing an rpath to the Subversion build process works around the
> issue, too:
> make EXTRA_LDFLAGS="-Wl,-rpath,$(PREFIX)/serf/lib"
> Before serf-1.3.0 this linker argument was handled by libtool.
> Can serf please be fixed so that this works out of the box again?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
