[syslog-ng] syslog-ng 3.15.1 on solaris

Szalai, Attila Attila.Szalai at morganstanley.com
Wed May 30 16:03:00 UTC 2018

´╗┐The trick here is that I saw this (kind of) issue on linux when I tried to merge the eventlog with the syslog-ng.

So I would like to keep my question. Do anybody tried to compile 3.15.1 on solaris? Was success?

If yes, then I can be sure the build system do something wrong. If not, I would like to do some test with a more vanilla build environment to check it (will not be easy).

Also I would like to emphasize that I build the linux version in the same build architecture. Which means that basic linking issues should had been seen there too.

> -----Original Message-----
> From: syslog-ng [mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of
> Sandor Geller
> Sent: Wednesday, May 30, 2018 5:40 PM
> To: syslog-ng at lists.balabit.hu
> Subject: Re: [syslog-ng] syslog-ng 3.15.1 on solaris
> Hello,
> On 05/30/2018 05:19 PM, Gergely Nagy wrote:
> > Hi!
> >
> >>>>>> "Attila" == Szalai, Attila <Attila.Szalai at morganstanley.com> writes:
> >      Attila> For me, it ended to linking process with this:
> >      Attila> ld: fatal: library -lsyslog-ng: not found
> >      Attila> collect2: error: ld returned 1 exit status
> >      Attila> libtool: install: error: relink `modules/diskq/libdisk-buffer.la' with
> the above command before installing it
> >
> > Would it be possible to share a full build log with V=1, and a list of
> > created artifacts? (building in a subdir and doing a find there after
> > compilation would be wonderful)
> >
> > I don't have any idea off the top of my head, but if I see what the
> > build produces or how, I might be able to figure something out. The
> > linking error alone is of little help :/
> >
> Wow... Being someone who was involved with syslog-ng @MS for years I
> guess the issue is that the configure-time prefix and the install-time
> prefix do differ so pachnames referenced in the .la files are not yet in
> existence (there is a proprietary software management system @MS which
> moves the freshly built stuff into its final run-time location which is
> read-only).
> I added a libtool hack to the MS-specific build helpers which edits
> libtool files during make install in the proper order to avoid rerunning
> configure (which would run this time with the install prefix causing
> trouble for the runtime).
> Regards,
> Sandor
> __________________________________________________________
> ____________________
> 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

NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained herein are not intended to be, and do not constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received this communication in error, please destroy all electronic and paper copies and notify the sender immediately. Mistransmission is not intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the extent permitted under applicable law, to monitor electronic communications. This message is subject to terms available at the following link: http://www.morganstanley.com/disclaimers  If you cannot access these links, please notify us by reply message and we will send the contents to you. By communicating with Morgan Stanley you consent to the foregoing and to the voice recording of conversations with personnel of Morgan Stanley.

More information about the syslog-ng mailing list