[syslog-ng] Things to consider when selecting latest syslog-ng version to linux
R.Naveen Naidu
naveenese at gmail.com
Fri Sep 7 08:48:05 UTC 2018
Hi,
I'm facing one more issue while cross-compiling the syslog-ng-3.17.2.
Actually, syslog-ng is cross-compiled in one server and another server its
failing due to "*glib-compile-schemas" is not there in PATH. *Both servers
are using different kernel versions.
For syslog-ng, I downloaded the glib-2.26.1 version as syslog-ng-3.17.2 is
expecting this min version of glib.
My doubt is Why it's using the local glib* packages during cross-compile?
Even in config file mentioned glib-schemas and marshal has to be there in
PATH
Do we need these binaries in local PATH before using glib-2.26.1 for
syslog-ng ? Please let me know your comments/suggestions ?
*File: glib-2.26.1/configure.ac <http://configure.ac> *
===
dnl ******************************************************************
dnl *** If we are cross-compiling, look for glib-genmarshal and ***
dnl *** glib-compile-schemas in PATH ***
dnl ******************************************************************
*AM_CONDITIONAL(CROSS_COMPILING, test $cross_compiling = yes)*
if test $cross_compiling = yes; then
AC_PATH_PROG(GLIB_GENMARSHAL, glib-genmarshal, no)
if test x$GLIB_GENMARSHAL = xno; then
AC_MSG_ERROR(Could not find a glib-genmarshal in your *PATH*)
fi
AC_PATH_PROG(GLIB_COMPILE_SCHEMAS, glib-compile-schemas, no)
if test x$GLIB_COMPILE_SCHEMAS = xno; then
AC_MSG_ERROR(Could not find a glib-compile-schemas in your PATH)
fi
fi
*LOGS for 2 servers:*
======
*Server #1*
*Server #2*
* uname -a*
Linux 1b23564ad2ef 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
*uname -a*
Linux ossbldrh6-bsn-01 2.6.32-279.22.1.el6.x86_64 #1 SMP Sun Jan 13
09:21:40 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
*Glib binaries*
[admin at 1b23564ad2ef XXXXX]$ *ls -l /usr/bin/glib-**
-rwxr-xr-x 1 root root 38496 Jun 19 15:42 /usr/bin/glib-compile-schemas
-rwxr-xr-x 1 root root 24664 Jun 19 15:42 /usr/bin/glib-genmarshal
-rwxr-xr-x 1 root root 5444 Jun 19 15:50 /usr/bin/glib-gettextize
-rwxr-xr-x 1 root root 16910 Jun 19 15:50 /usr/bin/glib-mkenums
*Glib binaries*
[nr023456 at ossbldrh6-bsn-01 syslog]$ *ls -l /usr/bin/glib-**
-rwxr-xr-x 1 root root 28312 Dec 21 2010 /usr/bin/glib-genmarshal
-rwxr-xr-x. 1 root root 5444 Dec 21 2010 /usr/bin/glib-gettextize
-rwxr-xr-x. 1 root root 15725 Dec 21 2010 /usr/bin/glib-mkenums
*NOTE: glib-compile-schemas is not there in bin location*
*Glib compile logs(generated logs during cross compile)*
checking whether to use assembler code for atomic operations... checking
whether GCC supports build-in atomic intrinsics... yes
checking for futex(2) system call... yes
checking value of POLLIN... 1
checking value of POLLOUT... 4
checking value of POLLPRI... 2
checking value of POLLERR... 8
checking value of POLLHUP... 16
checking value of POLLNVAL... 32
checking for broken poll... no (cross compiling)
checking whether compiler understands -Wno-pointer-sign... yes
checking for EILSEQ... yes
checking for glib-genmarshal... /usr/bin/glib-genmarshal
checking for glib-compile-schemas... /usr/bin/glib-compile-schemas
checking for gtkdoc-check... no
checking for gtkdoc-rebase... no
checking for gtkdoc-mkpdf... no
checking whether to build gtk-doc documentation... no
checking whether to include dtrace tracing support... yes
*Glib compile logs(generated logs during cross compile)*
checking for monotonic clocks... yes
checking whether to use assembler code for atomic operations... checking
whether GCC supports build-in atomic intrinsics... yes
checking for futex(2) system call... yes
checking value of POLLIN... 1
checking value of POLLOUT... 4
checking value of POLLPRI... 2
checking value of POLLERR... 8
checking value of POLLHUP... 16
checking value of POLLNVAL... 32
checking for broken poll... no (cross compiling)
checking whether compiler understands -Wno-pointer-sign... yes
checking for EILSEQ... yes
checking for glib-genmarshal... /usr/bin/glib-genmarshal
checking for glib-compile-schemas... no
configure: error: Could not find a glib-compile-schemas in your PATH
make[9]: *** [glib-2.26.1/config.status] Error 1
On Fri, Aug 24, 2018 at 9:05 PM R.Naveen Naidu <naveenese at gmail.com> wrote:
> Thanks Gabor.
> Java module is disabled now.
>
> Thanks
> Naveen
>
> On Fri, Aug 24, 2018 at 8:04 PM Nagy, Gábor <gabor.nagy at oneidentity.com>
> wrote:
>
>> Hi,
>>
>> I hope I understood your question, but to disable compiling java modules
>> you need to use the "--disable-java" configure option or the "
>> *enable-java*=no".
>> *enable_java *with underscore is the variable's name I think.
>>
>> Regards,
>> Gabor
>>
>> On Fri, Aug 24, 2018 at 4:23 PM R.Naveen Naidu <naveenese at gmail.com>
>> wrote:
>>
>>>
>>> Hi,
>>>
>>> Could you please help to disable the java modules while cross-compiling
>>> the syslog-ng(*3.17.2*). I tried disabling the java module(
>>> *--enable_java=no*) during configure and showing it as an
>>> unrecognized option(This is done in local syslog-ng compile Makefile where
>>> doing untar of syslog-ng and configure/make).
>>>
>>> From the below site given the given Java options if we need to use it.
>>>
>>> https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/administration-guide/10#TOPIC-956423
>>> ====
>>> *If you want to use the Java-based modules of syslog-ng OSE (for
>>> example, the Elasticsearch, HDFS, or Kafka destinations), you must compile
>>> syslog-ng OSE with Java support. *
>>> ====
>>> Mainly I don't want the Java to be cross-compiled and not going to use
>>> it. I see these options are there in configure.ac file.
>>> AC_ARG_ENABLE(java, [* --enable-java* Enable java destination
>>> (default: auto)],, enable_java="auto")
>>>
>>> *Error logs:*
>>> ===
>>> ./configure \
>>> <Some donfig options>
>>> * --enable_java=no \*
>>> --with-module-path="/lib:/lib/syslog-ng"
>>> configure: error: unrecognized option: `--enable_java=no'
>>> Try `./configure --help' for more information
>>>
>>> In *config.log *file below logs are there after compiling.
>>>
>>> * java : yes*
>>> * java modules : no*
>>> native bindings : auto
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Aug 21, 2018 at 2:40 PM R.Naveen Naidu <naveenese at gmail.com>
>>> wrote:
>>>
>>>> Thank you Gabor for pointing to correct page for a cross-compiling and
>>>> choose the dependencies.
>>>>
>>>> I will try this and get back you if any issues.
>>>>
>>>> On Tue, Aug 21, 2018 at 2:15 PM Nagy, Gábor <gabor.nagy at oneidentity.com>
>>>> wrote:
>>>>
>>>>> Hello!
>>>>>
>>>>> I think what needs to be considered is are the dependencies available
>>>>> on your platform?
>>>>> Here is a list of dependencies in our admin guide:
>>>>>
>>>>> https://www.syslog-ng.com/technical-documents/doc/syslog-ng-open-source-edition/3.16/administration-guide/10#TOPIC-956423
>>>>> The current required versions can be seen in configure.ac file.
>>>>>
>>>>> We have created a wiki page on github for a cross-compiling getting
>>>>> started:
>>>>> https://github.com/balabit/syslog-ng/wiki/Cross-compile-syslog-ng
>>>>>
>>>>> Regards,
>>>>> Gabor
>>>>>
>>>>> On Tue, Aug 21, 2018 at 9:42 AM R.Naveen Naidu <naveenese at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Added the sub.
>>>>>>
>>>>>> On Tue, Aug 21, 2018 at 1:07 PM R.Naveen Naidu <naveenese at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I need a help to choose the syslog-ng package for Linux.
>>>>>>>
>>>>>>> What are the things need to consider when choosing the latest
>>>>>>> syslog-ng to Linux?
>>>>>>>
>>>>>>> Actually, I wanted to cross-compile the syslog-ng and load into the
>>>>>>> customized Linux version *4.1.35rt41*
>>>>>>>
>>>>>>> The current latest syslog-ng version is* 3.17.2* from below site
>>>>>>> and planning to use this.
>>>>>>> https://github.com/balabit/syslog-ng/releases
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Thanks & Regards
>>>>>>> Naveen
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks & Regards
>>>>>> Naveen
>>>>>>
>>>>>> ______________________________________________________________________________
>>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>>>> Documentation:
>>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>>>
>>>>>>
>>>>> ______________________________________________________________________________
>>>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>>>> Documentation:
>>>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>>>
>>>>>
>>>>
>>>> --
>>>> Thanks & Regards
>>>> Naveen
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards
>>> Naveen
>>>
>>> ______________________________________________________________________________
>>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>>> Documentation:
>>> http://www.balabit.com/support/documentation/?product=syslog-ng
>>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>>
>>>
>> ______________________________________________________________________________
>> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
>> Documentation:
>> http://www.balabit.com/support/documentation/?product=syslog-ng
>> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>>
>>
>
> --
> Thanks & Regards
> Naveen
>
--
Thanks & Regards
Naveen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20180907/c7f60031/attachment-0001.html>
More information about the syslog-ng
mailing list