https://bugzilla.balabit.com/show_bug.cgi?id=173 kathi <jk_kathi1@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jk_kathi1@yahoo.com Status|NEEDINFO |REOPENED --- Comment #3 from kathi <jk_kathi1@yahoo.com> 2012-12-12 17:16:24 --- (In reply to comment #2)
Is this still and issue, or can I close it? I don't think this is a bug in syslog-ng...
I am facing the same issue while compiling syslog-ng-3.4.0-alpha3 on CentoOS 6.3 . First Eventlog gave an error checking for EVTLOG... no configure: error: Package requirements (eventlog >= 0.2.12) were not met: No package 'eventlog' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables EVTLOG_CFLAGS and EVTLOG_LIBS to avoid the need to call pkg-config. when i set the env varilable export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig , eventlog went through fine but glib gave errors checking for GLIB... no configure: error: Package requirements (glib-2.0 >= 2.10.1 gmodule-2.0 gthread-2.0) were not met: No package 'glib-2.0' found No package 'gmodule-2.0' found No package 'gthread-2.0' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables GLIB_CFLAGS and GLIB_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. after which i set the GLIB_LIBS=/lib64 and export GLIB_CFLAGS=/lib64:/usr/lib and the error while compiling is checking sanity checking Glib headers... no configure: error: Glib headers inconsistent with current compiler setting. You might be using 32 bit Glib with a 64 bit compiler, check PKG_CONFIG_PATH I have checked /lib64 , /usr/lib64 for glib2 , gmodule , gthread libraries Any clues how i can resolve this Thank you Kathi -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.