<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Mangal;
panose-1:2 4 5 3 5 2 3 3 2 2;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you. I will try as you suggested.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Girish<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu]
<b>On Behalf Of </b>Scheidler, Balázs<br>
<b>Sent:</b> Monday, February 15, 2016 3:34 PM<br>
<b>To:</b> Syslog-ng users' and developers' mailing list<br>
<b>Subject:</b> Re: [syslog-ng] syslog-ng 3.7.x support on armv7 architecture<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Either try to use a native compilation (like Czanik P recommended), or let's troubleshoot the toolchain issue.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">The error messages up there seems to indicate some problem in the assembly output generated by gcc. You could check that by asking gcc to output an assembly file (and not use a temporary) using the -S switch
to gcc.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Basically you should get the gcc command line that fails using:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">$ make V=1<br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">This will enable verbose logging, and all commands will be printed by make. Copy-paste the command line and<br>
1) supply an additional -S option, and <br>
2) locate and change the -o option to specify a output file name that you can investigate (e.g. -o foobar.s)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Then locate the lines 260 and 269, which cause the assembler to fail. You should be able to reproduce the problem by reassembling the same file:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">$ as <filename>.s<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Just by googling the error message I've found:<br>
<br>
<a href="https://mail-index.netbsd.org/netbsd-bugs/2014/05/28/msg036820.html">https://mail-index.netbsd.org/netbsd-bugs/2014/05/28/msg036820.html</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Which is a netbsd error report, but nevertheless probably a genuine bug in gcc 4.8.3<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">And also a syslog-ng specific workaround here:<br>
<br>
<a href="https://git.congatec.com/yocto/meta-openembedded/commit/c0ce7599526c4dce6d889fc4a5aa007f445e6d76">https://git.congatec.com/yocto/meta-openembedded/commit/c0ce7599526c4dce6d889fc4a5aa007f445e6d76</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">The 2nd seems to indicate that although the __thread keyword exists, it doesn't work. The patch in the 2nd link is not the best one, but if you are willing to test patches, I can work in improving it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Hope this helps,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Bazsi<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">-- <br>
Bazsi<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Sun, Feb 14, 2016 at 10:34 AM, Girish Kumar <<a href="mailto:girish.kumar@al-enterprise.com" target="_blank">girish.kumar@al-enterprise.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Thanks Peter.<br>
I started using syslog-ng 3.7.2.<br>
<br>
Armv7 hardware is BCM56340(Helix4) from broadcom<br>
My requirement is sending syslog messages over TLS to remote server.<br>
My compilation went fine for power pc architecture.<br>
But for ARMv7 I am having problem as I mentioned earlier.<br>
<br>
Following is the error. As other community friends suggested to I tried setting magic CFLAGS and LDFLAGS. But could not succeed.<br>
Could you please share your experience.<br>
<br>
CC lib/lib_libsyslog_ng_la-mainloop-call.lo<br>
/tmp/ccChQOWy.s: Assembler messages:<br>
/tmp/ccChQOWy.s:260: Error: invalid operands (.text and *UND* sections) for `-'<br>
/tmp/ccChQOWy.s:269: Error: invalid operands (.text and *UND* sections) for `-'<br>
make[4]: *** [lib/lib_libsyslog_ng_la-mainloop-call.lo] Error 1<br>
make[3]: *** [all-recursive] Error 1<br>
make[2]: *** [all] Error 2<br>
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'<br>
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'<br>
make --no-print-directory install-recursive<br>
CC lib/lib_libsyslog_ng_la-mainloop-call.lo<br>
/tmp/cc0N5KS5.s: Assembler messages:<br>
/tmp/cc0N5KS5.s:260: Error: invalid operands (.text and *UND* sections) for `-'<br>
/tmp/cc0N5KS5.s:269: Error: invalid operands (.text and *UND* sections) for `-'<br>
make[4]: *** [lib/lib_libsyslog_ng_la-mainloop-call.lo] Error 1<br>
make[3]: *** [install-recursive] Error 1<br>
make[2]: *** [install] Error 2<br>
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'<br>
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<br>
make[1]: Leaving directory `/home/gkuma020/PERFORCE/7.X.X.R01-gkuma020-gg/engr/sw/tps'<br>
make: *** [tps-build] Error 2<br>
+ set +x<br>
<br>
<br>
Regards,<br>
Girish<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: <a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a> [mailto:<a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>] On Behalf Of Czanik, Péter<br>
Sent: Friday, February 12, 2016 12:15 PM<br>
To: Syslog-ng users' and developers' mailing list<br>
Subject: Re: [syslog-ng] syslog-ng 3.7.x support on armv7 architecture<br>
<br>
Hi,<br>
<br>
Starting with syslog-ng 3.7, sources are only published on github.<br>
This is the current stable version, 3.8 is the current development version, which is now git head.<br>
<br>
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)<br>
<br>
Bye,<br>
Peter Czanik (CzP) <<a href="mailto:peter.czanik@balabit.com">peter.czanik@balabit.com</a>> Balabit / syslog-ng upstream
<a href="http://czanik.blogs.balabit.com/" target="_blank">http://czanik.blogs.balabit.com/</a>
<a href="https://twitter.com/PCzanik" target="_blank">https://twitter.com/PCzanik</a><br>
<br>
<br>
On Fri, Feb 12, 2016 at 7:31 AM, Girish Kumar <<a href="mailto:girish.kumar@al-enterprise.com">girish.kumar@al-enterprise.com</a>> wrote:<br>
> Thank you all for the information. I will start working based on your<br>
> suggestions.<br>
><br>
><br>
><br>
> Please let me know which version of syslog-ng I should use. I<br>
> downloaded both syslog-ng 3.7.2 and syslog-ng 3.6.4<br>
><br>
><br>
><br>
> I assume syslog-ng 3.6.4 is the stable version. Following website<br>
> doesn’t have syslog-ng 3.7.2<br>
><br>
><br>
><br>
> <a href="https://my.balabit.com/downloads/syslog-ng/sources" target="_blank">https://my.balabit.com/downloads/syslog-ng/sources</a><br>
><br>
><br>
><br>
><br>
><br>
> Regards,<br>
><br>
> Girish<br>
><br>
><br>
><br>
> From: <a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a><br>
> [mailto:<a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>] On Behalf Of Scheidler,<br>
> Balázs<br>
> Sent: Wednesday, February 10, 2016 6:02 PM<br>
> To: Syslog-ng users' and developers' mailing list<br>
> Subject: Re: [syslog-ng] syslog-ng 3.7.x support on armv7 architecture<br>
><br>
><br>
><br>
> Hi Girish,<br>
><br>
> Those architectures that are listed were known to work in specific<br>
> points in time and are not guaranteed to remain so. Also, syslog-ng is<br>
> an application written in C and is aimed to be portable to a number of<br>
> architectures, which we also demonstrated in the amount of platforms that we support.<br>
><br>
> On this community mailing list, all we can do is help you if you have<br>
> specific questions/issues. This may or may not match your level of<br>
> expectations, but we can only guarantee that we put "best effort" in<br>
> answering your questions and no guarantees.<br>
><br>
> Back to armv7, just like Peter Czanik has answered, we know about<br>
> syslog-ng being used on this architecture, so it should theoretically<br>
> be possible, but it's not something that the developers use every day,<br>
> or which would be a primary platform (those being Linux distributions).<br>
><br>
> The toolchain and the environment matters, syslog-ng depends on a<br>
> number of external libraries (glib for example, which you had an issue<br>
> with in the past), and we generally assume that those are present on the system already.<br>
><br>
> That being said, Balabit does provide support for various platforms<br>
> and as a commercial entity has the means and willingness to do testing<br>
> in a wider variety of platforms and architectures. If you would like<br>
> support guarantees, Balabit can most probably give that.<br>
><br>
><br>
><br>
> The best course of action seems to be for you to:<br>
><br>
> 1) continue your trial and error in compiling syslog-ng, and ask if<br>
> there's a concrete issue. We will answer to the best of our ability.<br>
><br>
> 2) try contacting Balabit sales if the response you get on this<br>
> mailing list is not enough to get your issues resolved.<br>
><br>
> I am really happy to help, just like I did in the past.<br>
><br>
> Disclaimer: I am employed by Balabit (being the CTO there), however I<br>
> wrote this email as a member of the open source syslog-ng community. I<br>
> don't want to push anything here, the only reason I wrote this email<br>
> is that I started sensing a mismatch of what the community can provide<br>
> and what you can expect.<br>
><br>
> I hope this helps,<br>
><br>
> Bazsi<br>
><br>
><br>
><br>
><br>
> --<br>
> Bazsi<br>
><br>
><br>
><br>
> On Wed, Feb 10, 2016 at 12:25 PM, Girish Kumar<br>
> <<a href="mailto:girish.kumar@al-enterprise.com">girish.kumar@al-enterprise.com</a>> wrote:<br>
><br>
> Hi All,<br>
><br>
><br>
><br>
> Please let me know whether syslog-ng 3.7.x is supported on armv7<br>
> architecture.<br>
><br>
> I went through the following link and found that armv7 is not listed<br>
><br>
><br>
><br>
> <a href="https://www.balabit.com/sites/default/files/documents/syslog-ng-ose-la" target="_blank">
https://www.balabit.com/sites/default/files/documents/syslog-ng-ose-la</a><br>
> test-guides/en/syslog-ng-ose-guide-admin/html/supported-platforms.html<br>
><br>
><br>
><br>
> 1.6. Supported platforms<br>
><br>
> The syslog-ng Open Source Edition application is highly portable and<br>
> is known to run on a wide range of hardware architectures (x86,<br>
> x86_64, SUN Sparc, PowerPC 32 and 64, Alpha)<br>
><br>
><br>
><br>
> Regards,<br>
><br>
> Girish<br>
><br>
><br>
> ______________________________________________________________________<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">> ________ Member info:<br>
> <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
> Documentation:<br>
> <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">
http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
> FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
><br>
><br>
><br>
><br>
> ______________________________________________________________________<br>
> ________ Member info:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">> <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">
https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
> Documentation:<br>
> <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">
http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
> FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
><br>
><br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">
https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">
http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">
https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">
http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>