[syslog-ng] syslog-ng 3.7.x support on armv7 architecture

Thu Feb 18 15:11:02 CET 2016

You do not need libjson, but in that case system() source will not work:
you need to specify system related log sources by hand.

You can also disable some bundled libraries to save space, just add a few
more configure options (you better check the spelling): --disable-mongodb
--disable-amqp

Bye,

Peter Czanik (CzP) <peter.czanik at balabit.com>
Balabit / syslog-ng upstream
http://czanik.blogs.balabit.com/
https://twitter.com/PCzanik

On Thu, Feb 18, 2016 at 3:05 PM, Girish Kumar <
girish.kumar at al-enterprise.com> wrote:

> Thanks Czanik  for detailed information.
>
> I have included following libraries . Please let me know if this is ok.  I
> have not included libjson.
>
> ·         EVTLOG
>
> ·         GLIB
>
> ·         PCRE
>
> ·         OPENSSL
>
>
>
> Since my requirement is  sending syslog  log messages over TLS and it is
> on embedded systems I have to include minimum number of libraries.
>
> Please let me know if any of the libraries can be removed
>
>
>
> Regards,
>
> Girish
>
>
>
> *From:* syslog-ng-bounces at lists.balabit.hu [mailto:
> syslog-ng-bounces at lists.balabit.hu] *On Behalf Of *Czanik, Péter
> *Sent:* Monday, February 15, 2016 12:59 AM
>
> *To:* Syslog-ng users' and developers' mailing list
> *Subject:* Re: [syslog-ng] syslog-ng 3.7.x support on armv7 architecture
>
>
>
> Hi,
>
>
> I never did cross compiling, so I can't help you in that one, but
> compiling nativity on a Raspberry Pi 2 using an up-to-date Raspbian as OS
> worked fine. First I installed all development dependencies, downloaded an
> unpacked sources. Next I ran configure with python support disabled (did
> not have time to debug why configure failed to find python, but most likely
> you don't need it anyway in an embedded environment). Next I built it and
> ran make check to see if self check succeeds. Everything was all right.
> Make install put the whole thing under /usr/local. As it's the only
> software there, it's easy to remove it using 'find /usr/local -type f
> -delete' :)
>
> apt-get install gcc make flex bison libssl-dev libglib2.0-dev autoconf
> libtool libevtlog-dev libjson0-dev
>
> wget
> https://github.com/balabit/syslog-ng/releases/download/syslog-ng-3.7.2/syslog-ng-3.7.2.tar.gz
>
> tar xzvpf syslog-ng-3.7.2.tar.gz
>
> cd syslog-ng-3.7.2
>
> ./configure --disable-python
>
> make
>
> make check
>
> make install
>
>
>
> root at raspberrypi:/home/pi/syslog-ng-3.7.2# uname -a
> Linux raspberrypi 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015
> armv7l GNU/Linux
> root at raspberrypi:/home/pi/syslog-ng-3.7.2# /usr/local/sbin/syslog-ng -V
> syslog-ng 3.7.2
> Installer-Version: 3.7.2
> Revision:
> Compile-Date: Feb 14 2016 17:55:46
> Available-Modules:
> basicfuncs,pseudofile,csvparser,affile,kvformat,json-plugin,afamqp,afprog,syslogformat,afuser,graphite,confgen,afstomp,cryptofuncs,afmongodb,afsocket,linux-kmsg-format,system-source,dbparser,sdjournal
> Enable-Debug: off
> Enable-GProf: off
> Enable-Memtrace: off
> Enable-IPv6: on
> Enable-Spoof-Source: off
> Enable-TCP-Wrapper: off
> Enable-Linux-Caps: off
>
> All of this is documented at
> https://www.balabit.com/sites/default/files/documents/syslog-ng-ose-3.7-guides/en/syslog-ng-ose-v3.7-guide-admin/html-single/index.html#compiling-syslog-ng
>
> Bye,
>
>
> Peter Czanik (CzP) <peter.czanik at balabit.com>
> Balabit / syslog-ng upstream
> http://czanik.blogs.balabit.com/
> https://twitter.com/PCzanik
>
>
>
> On Sun, Feb 14, 2016 at 10:34 AM, Girish Kumar <
> girish.kumar at al-enterprise.com> wrote:
>
> Thanks Peter.
> I started using syslog-ng 3.7.2.
>
> Armv7 hardware is BCM56340(Helix4) from broadcom
> My requirement is sending syslog messages over TLS to remote server.
> My compilation went fine for power pc architecture.
> But  for ARMv7 I am having problem as I  mentioned earlier.
>
> Following is the error. As other community friends suggested to I tried
> setting magic CFLAGS and LDFLAGS. But could not succeed.
> Could you please share your experience.
>
>   CC     lib/lib_libsyslog_ng_la-mainloop-call.lo
> /tmp/ccChQOWy.s: Assembler messages:
> /tmp/ccChQOWy.s:260: Error: invalid operands (.text and *UND* sections)
> for `-'
> /tmp/ccChQOWy.s:269: Error: invalid operands (.text and *UND* sections)
> for `-'
> make[4]: *** [lib/lib_libsyslog_ng_la-mainloop-call.lo] Error 1
> make[3]: *** [all-recursive] Error 1
> make[2]: *** [all] Error 2
> make[2]: Leaving directory
> `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/objs/46/7.X.X.R01/armv7/syslog-ng'
> make[2]: Entering directory
> `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/objs/46/7.X.X.R01/armv7/syslog-ng'
> make --no-print-directory install-recursive
>   CC     lib/lib_libsyslog_ng_la-mainloop-call.lo
> /tmp/cc0N5KS5.s: Assembler messages:
> /tmp/cc0N5KS5.s:260: Error: invalid operands (.text and *UND* sections)
> for `-'
> /tmp/cc0N5KS5.s:269: Error: invalid operands (.text and *UND* sections)
> for `-'
> make[4]: *** [lib/lib_libsyslog_ng_la-mainloop-call.lo] Error 1
> make[3]: *** [install-recursive] Error 1
> make[2]: *** [install] Error 2
> make[2]: Leaving directory
> `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/objs/46/7.X.X.R01/armv7/syslog-ng'
> make[1]: ***
> [/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps/built/46/7.X.X.R01/armv7/sbin/syslog-ng]
> Error 2
> make[1]: Leaving directory
> `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps'
> make: *** [tps-build] Error 2
> + set +x
>
>
> Regards,
> Girish
>
>
> -----Original Message-----
> From: syslog-ng-bounces at lists.balabit.hu [mailto:
> syslog-ng-bounces at lists.balabit.hu] On Behalf Of Czanik, Péter
> Sent: Friday, February 12, 2016 12:15 PM
> To: Syslog-ng users' and developers' mailing list
> Subject: Re: [syslog-ng] syslog-ng 3.7.x support on armv7 architecture
>
> Hi,
>
> Starting with syslog-ng 3.7, sources are only published on github.
> This is the current stable version, 3.8 is the current development
> version, which is now git head.
>
> BTW: could you write about your use case? On which ARMv7 hardware do you
> use syslog-ng? How do you (plan to) use it? (I'm an ARM addict, running
> syslog-ng on the Raspberry Pi2)
>
> Bye,
> Peter Czanik (CzP) <peter.czanik at balabit.com> Balabit / syslog-ng
> upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik
>
>
> On Fri, Feb 12, 2016 at 7:31 AM, Girish Kumar <
> girish.kumar at al-enterprise.com> wrote:
> > Thank you all for the information. I will start working based on your
> > suggestions.
> >
> >
> >
> > Please let me know which version of syslog-ng I should use.  I
> > downloaded both syslog-ng 3.7.2 and syslog-ng 3.6.4
> >
> >
> >
> > I assume syslog-ng 3.6.4 is  the stable version. Following website
> > doesn’t have syslog-ng 3.7.2
> >
> >
> >
> > https://my.balabit.com/downloads/syslog-ng/sources
> >
> >
> >
> >
> >
> > Regards,
> >
> > Girish
> >
> >
> >
> > From: syslog-ng-bounces at lists.balabit.hu
> > [mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Scheidler,
> > Balázs
> > Sent: Wednesday, February 10, 2016 6:02 PM
> > To: Syslog-ng users' and developers' mailing list
> > Subject: Re: [syslog-ng] syslog-ng 3.7.x support on armv7 architecture
> >
> >
> >
> > Hi Girish,
> >
> > Those architectures that are listed were known to work in specific
> > points in time and are not guaranteed to remain so. Also, syslog-ng is
> > an application written in C and is aimed to be portable to a number of
> > architectures, which we also demonstrated in the amount of platforms
> that we support.
> >
> > On this community mailing list, all we can do is help you if you have
> > specific questions/issues. This may or may not match your level of
> > expectations, but we can only guarantee that we put "best effort" in
> > answering your questions and no guarantees.
> >
> > Back to armv7, just like Peter Czanik has answered, we know about
> > syslog-ng being used on this architecture, so it should theoretically
> > be possible, but it's not something that the developers use every day,
> > or which would be a primary platform (those being Linux distributions).
> >
> > The toolchain and the environment matters, syslog-ng depends on a
> > number of external libraries (glib for example, which you had an issue
> > with in the past), and we generally assume that those are present on the
> system already.
> >
> > That being said, Balabit does provide support for various platforms
> > and as a commercial entity has the means and willingness to do testing
> > in a wider variety of platforms and architectures. If you would like
> > support guarantees, Balabit can most probably give that.
> >
> >
> >
> > The best course of action seems to be for you to:
> >
> > 1) continue your trial and error in compiling syslog-ng, and ask if
> > there's a concrete issue. We will answer to the best of our ability.
> >
> > 2) try contacting Balabit sales if the response you get on this
> > mailing list is not enough to get your issues resolved.
> >
> > I am really happy to help, just like I did in the past.
> >
> > Disclaimer: I am employed by Balabit (being the CTO there), however I
> > wrote this email as a member of the open source syslog-ng community. I
> > don't want to push anything here, the only reason I wrote this email
> > is that I started sensing a mismatch of what the community can provide
> > and what you can expect.
> >
> > I hope this helps,
> >
> > Bazsi
> >
> >
> >
> >
> > --
> > Bazsi
> >
> >
> >
> > On Wed, Feb 10, 2016 at 12:25 PM, Girish Kumar
> > <girish.kumar at al-enterprise.com> wrote:
> >
> > Hi All,
> >
> >
> >
> > Please let me know whether syslog-ng 3.7.x is supported on armv7
> > architecture.
> >
> > I went through the  following link and found  that armv7 is not listed
> >
> >
> >
> > https://www.balabit.com/sites/default/files/documents/syslog-ng-ose-la
> > test-guides/en/syslog-ng-ose-guide-admin/html/supported-platforms.html
> >
> >
> >
> > 1.6. Supported platforms
> >
> > The syslog-ng Open Source Edition application is highly portable and
> > is known to run on a wide range of hardware architectures (x86,
> > x86_64, SUN Sparc, PowerPC 32 and 64, Alpha)
> >
> >
> >
> > Regards,
> >
> > Girish
> >
> >
> > ______________________________________________________________________
>
> > ________ 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
> >
> >
>
> ______________________________________________________________________________
> 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
>
>
>
>
> ______________________________________________________________________________
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20160218/186afc94/attachment-0001.htm 