[syslog-ng] pdbtool patternize update and my syslog-ng 3.2 branch

[Matthew Hall]

On Wed, Sep 29, 2010 at 11:06:18AM +0200, Balazs Scheidler wrote:
> If you can install the static versions of these libraries:
> 
> $GLIB_LIBS $EVTLOG_LIBS $PCRE_LIBS $REGEX_LIBS
> 
> Then those dependencies will be statically linked into the
> syslog-ng/pdbtool binary, but libsyslog-ng.so will always be linked
> dynamically. Not to mention that even pdbtool tries to load plugins.

OK Good to know. It might help if you were comfortable to publish a copy 
of the dpkg --get-selections output from one of your working build 
systems or a list of the dependencies which are needed to build this 
thing the right way. It's not exactly very easy to figure out when you 
want portable binaries. Especially since the build succeeds and produces 
unexpected output when certain libraries are missing.

> So as of right now, you can't move the binaries to different boxes.

Then how is Balabit able to produce packages which work on different 
boxes? Would it make a difference if I compiled on one box, copied the 
compiled tree, and then ran make install? That was what came to my mind 
as an ugly but possible effective technique.

> But I have good news as well, I've integrated gyp's patches to 
> mainline, cleaned them up, removed memory leaks and also decreased 
> memory usage a lot. So you don't need gyp's tree, it is enough to use 
> the mainline.

This is wonderful news. How would I get a nightly build of this if it's 
not possible for me to move the binaries from a system where it compiles 
(Ubuntu 10.04 LTS for example) to a system where it doesn't (RHEL 4 and 
5 for example)?

> Bazsi

Matthew.