[syslog-ng] syslog-ng 3.3.4 Coredumps on AIX 5.2
Sandor.Geller at morganstanley.com
Fri Jun 15 13:22:03 CEST 2012
Without a stacktrace it's impossible to tell what went wrong. Why do
you suspect glib in the first place???
If you used a compiler other than gcc and built a 64-bit executable
then you should take a look at the 'Problem with Syslog-NG 3.2.5 on
Aix 7.1 ... It coredumps..' thread in the list archive, back in March.
On Fri, Jun 15, 2012 at 1:02 PM, Divya Vikraman
<divya.divyavikram at gmail.com> wrote:
> Hello ALL,
> I have compiled syslog-ng 3.3.4 version using dynamic linking. But , while
> trying to run syslog-ng it coredumps
> # /opt/soe/local/syslog-ng-3.3.4/sbin/syslog-ng -F
> Memory fault(coredump)
> I have compiled glib-2.19.7 with the (--enable-static and --with-libiconv)
> After searching over the net for some possibel solutions , i found that a
> possible solution for this is to use the AIX libiconv instead of the GNU
> If this is correct, then the issue is , glib-2 needs the GNU glib, if i try
> with the system one the make fails with the below error.
> "error GNU libiconv not in use but included iconv.h is from libiconv".
> So, I cannot use the system libiconv as glib-2 will fail to compile and if I
> use GNU libiconv syslog-ng coredumps. though, the configure and stages do
> not complaing anything.
> Has, anyone else faced this issue , please let me know how can I get this
> Best Regards,
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
More information about the syslog-ng