I was scratching my head on that very issue a few hours ago. Its controlled by --with-module-dir

-Patrick

Sent: Wed Dec 01 2010 16:59:56 GMT-0700 (Mountain Standard Time)
From: Matthew Hall <mhall@mhcomputing.net>
To: syslog-ng@lists.balabit.hu
Subject: [syslog-ng] --libdir misbehaves
I'm compiling syslog-ng 3.2 beta 1. I'm going to update to 3.2 release 
briefly, maybe it's fixed in there? Even though I used:

--libdir=/home/opt/lib64

The syslog-ng plugins are still going into lib. I can't make an internal 
package of the app to use here until I figure out how to fix it. The 
files in question are:

/home/opt/lib/syslog-ng
/home/opt/lib/syslog-ng/libafsocket-tls.la
/home/opt/lib/syslog-ng/libafprog.la
/home/opt/lib/syslog-ng/libaffile.la
/home/opt/lib/syslog-ng/libaffile.so
/home/opt/lib/syslog-ng/libpacctformat.so
/home/opt/lib/syslog-ng/libsyslogformat.so
/home/opt/lib/syslog-ng/libafsql.so
/home/opt/lib/syslog-ng/libbasicfuncs.so
/home/opt/lib/syslog-ng/libafsocket.so
/home/opt/lib/syslog-ng/libafsocket-notls.la
/home/opt/lib/syslog-ng/libdbparser.la
/home/opt/lib/syslog-ng/libafuser.la
/home/opt/lib/syslog-ng/libconvertfuncs.la
/home/opt/lib/syslog-ng/libbasicfuncs.la
/home/opt/lib/syslog-ng/libcsvparser.la
/home/opt/lib/syslog-ng/libafprog.so
/home/opt/lib/syslog-ng/libafsql.la
/home/opt/lib/syslog-ng/libpacctformat.la
/home/opt/lib/syslog-ng/libafsocket-tls.so
/home/opt/lib/syslog-ng/libdbparser.so
/home/opt/lib/syslog-ng/libdummy.la
/home/opt/lib/syslog-ng/libcsvparser.so
/home/opt/lib/syslog-ng/libconvertfuncs.so
/home/opt/lib/syslog-ng/libafsocket-notls.so
/home/opt/lib/syslog-ng/libconfgen.so
/home/opt/lib/syslog-ng/libafuser.so
/home/opt/lib/syslog-ng/libsyslogformat.la
/home/opt/lib/syslog-ng/libconfgen.la
/home/opt/lib/syslog-ng/libdummy.so
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.campin.net/syslog-ng/faq.html