On Mon, Jul 04, 2011 at 09:07:49PM +0200, Rainer Jung wrote:
Hi everyone,
a couple of modules have additional external dependencies:
mod_deflate: zlib
mod_lua: lua
mod_serf: serf
mod_socache_dc: distcache
At the moment, the compiled modules do not contain any RPATH/RUNPATH
info
Hi Joe,
On 05.07.2011 09:46, Joe Orton wrote:
On Mon, Jul 04, 2011 at 09:07:49PM +0200, Rainer Jung wrote:
Hi everyone,
a couple of modules have additional external dependencies:
mod_deflate: zlib
mod_lua: lua
mod_serf: serf
mod_socache_dc: distcache
At the moment, the compiled modules
I will think about a good way, how users can pass additional LDADD
flags. Putting the -R ... into the LDFLAGS seems to be too heavy,
because then the RPATH of every module etc. will contain the given
directory. The real problematic cases are only mod_lua and in rare
circumstances (you want to
On Tue, Jul 05, 2011 at 11:25:53AM +0200, Rainer Jung wrote:
I will think about a good way, how users can pass additional LDADD
flags. Putting the -R ... into the LDFLAGS seems to be too heavy,
because then the RPATH of every module etc. will contain the given
directory. The real
On 7/5/2011 2:46 AM, Joe Orton wrote:
IMO it is much better to leave this stuff in the control of people who
build the software, who can already set env vars or LDFLAGS as they
require. (It would also be much better if everybody used libtool, since
as you say, the .la files make this
Hi everyone,
a couple of modules have additional external dependencies:
mod_deflate: zlib
mod_lua: lua
mod_serf: serf
mod_socache_dc: distcache
At the moment, the compiled modules do not contain any RPATH/RUNPATH
info except when the libraries themselves are installed as libtool
libraries, i.e.