[syslog-ng] syslog-ng make errors on RHEL4 x86_64

[John Reddy]

I have found it very useful to compile syslog-ng from SRC RPMs I grab 
off rpm.pbone.net.  I had installed prior to build: 
rpm-build-4.3.3-18_nonptl, glib2-2.4.7-1, gcc-3.4.6-3, bison-1.875c-2, 
flex-2.5.4a-33

wget 
ftp://ftp.pbone.net/mirror/ftp.silfreed.net/repo/rhel/4/i386/silfreednet/SRPMS/eventlog-0.2.5-1.src.rpm
rpm -i eventlog-0.2.5-1.src.rpm
wget 
ftp://ftp.pbone.net/mirror/ftp.silfreed.net/repo/rhel/4/i386/silfreednet/SRPMS/syslog-ng-2.0.0-1.src.rpm
rpm -i syslog-ng-2.0.0-1.src.rpm
rpmbuild -bb /usr/src/redhat/SPECS/eventlog.spec
rpm -i /usr/src/redhat/RPMS/x86_64/eventlog-0.2.5-1.x86_64.rpm 
/usr/src/redhat/RPMS/x86_64/eventlog-devel-0.2.5-1.x86_64.rpmrpmbuild 
-bb /usr/src/redhat/SPECS/syslog-ng.spec
rpm -i /usr/src/redhat/RPMS/x86_64/syslog-ng-2.0.0-1.x86_64.rpm 
/usr/src/redhat/RPMS/x86_64/syslog-ng-vim-2.0.0-1.x86_64.rpm


I've also found that the default configuration of SELinux with RHEL4 is 
fairly restrictive, preventing logging outside of /var/log or logging 
outside the file system that hosts /var/log, preventing /proc/kmsg from 
being read, or allowing syslog to console.  If you must run SELinux, you 
might want to run:
# Allow logging to console
/usr/sbin/setsebool -P allow_syslog_to_console 1
# Allow logging to files/directories outside of /var/log
/usr/sbin/setsebool -P syslogd_disable_trans 1
# Allow access to reading /proc/kmsg
/usr/sbin/setsebool -P use_syslogng 1

Hope this helps some.

-John


On 12/10/2006 10:20 PM James Young said the following:
> When attempting to perform make on RHEL4 x86_64 for syslog-ng 2.0.0 I 
> recieve the following errors.  I have managed to find a previous post 
> in July which mentions patching the source, however the attachment has 
> been 'scrubbed' from the message.
>  
> Anyone able to point me toward what I need to be doing to resolve 
> these errors below?
>  
> libsyslog-ng.a(misc.o)(.text+0x3d1): In function `resolve_hostname':
> /var/tmp/syslog-ng-2.0.0/src/misc.c:178: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(logmsg.o)(.text+0x97): In function `log_stamp_format':
> /var/tmp/syslog-ng-2.0.0/src/logmsg.c:111: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(logmsg.o)(.text+0x37e): In function `log_msg_ref':
> /var/tmp/syslog-ng-2.0.0/src/logmsg.c:489: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(logmsg.o)(.text+0x41f): In function `log_msg_unref':
> /var/tmp/syslog-ng-2.0.0/src/logmsg.c:503: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(logmsg.o)(.text+0xd8b): In function 
> `log_msg_ack_block_end':
> /var/tmp/syslog-ng-2.0.0/src/logmsg.c:623: undefined reference to 
> `g_return_if_fail_warning'
> libsyslog-ng.a(logpipe.o)(.text+0x58): In function `log_pipe_ref':
> /var/tmp/syslog-ng-2.0.0/src/logpipe.c:38: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(logpipe.o)(.text+0xa9): In function `log_pipe_unref':
> /var/tmp/syslog-ng-2.0.0/src/logpipe.c:47: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(center.o)(.text+0x9f): In function `log_endpoint_free':
> /var/tmp/syslog-ng-2.0.0/src/center.c:90: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(center.o)(.text+0x18d): In function `log_connection_new':
> /var/tmp/syslog-ng-2.0.0/src/center.c:132: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(templates.o)(.text+0x358): In function `log_template_ref':
> /var/tmp/syslog-ng-2.0.0/src/templates.c:169: undefined reference to 
> `g_assert_warning'
> libsyslog-ng.a(templates.o)(.text+0x3bd):/var/tmp/syslog- 
> ng-2.0.0/src/templates.c:180: more undefined references to 
> `g_assert_warning' follow
> collect2: ld returned 1 exit status
> make[2]: *** [syslog-ng] Error 1
> make[2]: Leaving directory `/var/tmp/syslog-ng-2.0.0/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/var/tmp/syslog-ng-2.0.0'
> make: *** [all] Error 2

-- 
John Reddy
jreddy at bnl.gov
(631) 344-3284
Technology Architect
ITD Unix Services
Brookhaven National Labs