I think I know the source of the problem. (with my very limited knowledge) It looks like I have both the 32 & 64bit versions of GLIB2 installed and the configure script is picking up the 32bit version instead of the 64bit. I've compared Tim's config.log with mine and can see differences like this: Tims: CPPFLAGS=' -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64' Mine: CPPFLAGS=' -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/eventlog -D_BSD_SOURCE -D__BSD_SOURCE -D__FAVOR_BSD -DHAVE_NET_ETHERNET_H -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64' I don't have /usr/include/glib-2.0, so in my case it is picking up /usr/lib/glib-2.0/include. In Tim's case /usr/lib64/glib-2.0/include So question is why is the configure script not picking up my 64bit libraries? I suspect this is my binary seg faults... How do I force ./configure to use /usr/lib64/glib-2.0/include instead of /usr/lib/glib-2.0/include? Daniel -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Tim Boyer Sent: Monday, 12 November 2007 2:08 PM To: 'Syslog-ng users' and developers' mailing list' Subject: Re: [syslog-ng] Syslog-ng-2.05 Segmentation Fault
Tim,
Is there any chance you can send me a copy of your ./configure output (& options) when you compiled syslog-ng?
I want to compare it to mine.
I updated my system to reflect the same versions as your below. Recompiled again, but still syslog-ng still seg faults. Something has to be different!
Simple as it gets... env PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure I'll email you the config.log. -- tim -- _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html This email and any attachments transmitted with it are confidential and may contain legally privileged information. If you are not the intended recipient you are prohibited from disclosing, copying or using the information contained in it. If you have received this email in error, please notify the sender immediately by return email and then delete all copies of this transmission together with any attachments. It is the addressee's/recipient's duty to virus scan and otherwise test the email before loading it onto any computer system. IMC Communications does not accept liability in connection with any computer virus, data corruption, delay, interruption, unauthorised access or unauthorised amendment in relation to this email. For information about our privacy policy, visit the IMC Communications website at www.imc.net.au This email has been checked by IMC's SMTP gateway. -&-