gcc -g -O2 -Wall -g -o syslog-ng main.o libsyslog-ng.a -lnsl -lrt -Wl,-Bstatic -lfl -L/home/kundapur/GLIB-2.12.9/lib -lglib-2.0 -L/usr/local/lib -levtlog -lwrap -Wl,-Bdynamic libsyslog-ng.a(misc.o)(.text+0x3a9): In function `resolve_hostname': /home/kundapur/suma/syslog-ng-2.0.4/src/misc.c:191: undefined reference to `g_assert_warning' libsyslog-ng.a(logmsg.o)(.text+0x6a): In function `log_stamp_format': /home/kundapur/suma/syslog-ng-2.0.4/src/logmsg.c:110: undefined reference to `g_assert_warning' libsyslog-ng.a(logmsg.o)(.text+0x2b6): In function `log_msg_ref': /home/kundapur/suma/syslog-ng-2.0.4/src/logmsg.c:498: undefined reference to `g_assert_warning' libsyslog-ng.a(logmsg.o)(.text+0x342): In function `log_msg_unref': /home/kundapur/suma/syslog-ng-2.0.4/src/logmsg.c:512: undefined reference to `g_assert_warning' libsyslog-ng.a(logmsg.o)(.text+0xe36): In function `log_msg_ack_block_end': /home/kundapur/suma/syslog-ng-2.0.4/src/logmsg.c:648: undefined reference to `g_return_if_fail_warning' libsyslog-ng.a(logpipe.o)(.text+0x4f): In function `log_pipe_ref': /home/kundapur/suma/syslog-ng-2.0.4/src/logpipe.c:38: undefined reference to `g_assert_warning' libsyslog-ng.a(logpipe.o)(.text+0x9b): In function `log_pipe_unref': /home/kundapur/suma/syslog-ng-2.0.4/src/logpipe.c:47: undefined reference to `g_assert_warning' libsyslog-ng.a(center.o)(.text+0x7d): In function `log_endpoint_free': /home/kundapur/suma/syslog-ng-2.0.4/src/center.c:90: undefined reference to `g_assert_warning' libsyslog-ng.a(center.o)(.text+0x175): In function `log_connection_new': /home/kundapur/suma/syslog-ng-2.0.4/src/center.c:132: undefined reference to `g_assert_warning' libsyslog-ng.a(templates.o)(.text+0x2de): In function `log_template_ref': /home/kundapur/suma/syslog-ng-2.0.4/src/templates.c:180: undefined reference to `g_assert_warning' libsyslog-ng.a(templates.o)(.text+0x346):/home/kundapur/suma/syslog-ng-2.0.4/src/templates.c:191: more undefined references to `g_assert_warning' follow collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/kundapur/suma/syslog-ng-2.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/kundapur/suma/syslog-ng-2.0.4' make: *** [all] Error 2 I installed glib-2.12.9. -- $ cat glib.c # include <glib.h> int main ( void ) { printf ( "glib version = %d.%d.%d\n", glib_major_version, glib_minor_version, glib_micro_version ); return 0; } $ cc glib.c `pkg-config --cflags --libs glib-2.0` $ a.out glib version = 2.12.9 -- Still I'm getting these messages. Any idea about this? Thanks, Ganesh
gcc -g -O2 -Wall -g -o syslog-ng main.o libsyslog-ng.a -lnsl -lrt -Wl,-Bstatic -lfl -L/home/kundapur/GLIB-2.12.9/lib -lglib-2.0 -L/usr/local/lib -levtlog -lwrap -Wl,-Bdynamic
Here you're trying to build against a static glib-2.0
$ cat glib.c # include <glib.h>
int main ( void ) { printf ( "glib version = %d.%d.%d\n", glib_major_version, glib_minor_version, glib_micro_version );
return 0; } $ cc glib.c `pkg-config --cflags --libs glib-2.0` $ a.out glib version = 2.12.9
While this might be a dynamically linked executable. So I suppose you're missing the static glib library. Regards, Sandor -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
Hi, Thanks for the response. I configured with the option "--enable-dynamic-linking" and it worked. Could anybody please tell me how to get the year field in the log messages by using syslog-ng. Thanks, Ganesh On 7/17/07, Geller, Sandor (IT) <Sandor.Geller@morganstanley.com> wrote:
gcc -g -O2 -Wall -g -o syslog-ng main.o libsyslog-ng.a -lnsl -lrt -Wl,-Bstatic -lfl -L/home/kundapur/GLIB-2.12.9/lib -lglib-2.0 -L/usr/local/lib -levtlog -lwrap -Wl,-Bdynamic
Here you're trying to build against a static glib-2.0
$ cat glib.c # include <glib.h>
int main ( void ) { printf ( "glib version = %d.%d.%d\n", glib_major_version, glib_minor_version, glib_micro_version );
return 0; } $ cc glib.c `pkg-config --cflags --libs glib-2.0` $ a.out glib version = 2.12.9
While this might be a dynamically linked executable. So I suppose you're missing the static glib library.
Regards,
Sandor --------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
If you're still looking for how to get the year in log messages, you can use $YEAR or $FULLDATE, which includes the year. Check the reference manual included with the source code for the other macros that are available. Regards, Anthony
"Ganesh Kundapur" <ganesh.kundapur@gmail.com> 07/18/07 12:48 AM >>> Hi, Thanks for the response. I configured with the option "-- enable- dynamic- linking" and it worked.
Could anybody please tell me how to get the year field in the log messages by using syslog- ng. Thanks, Ganesh On 7/17/07, Geller, Sandor (IT) <Sandor.Geller@morganstanley.com> wrote:
gcc - g - O2 - Wall - g - o syslog- ng main.o libsyslog- ng.a - lnsl - lrt - Wl,- Bstatic - lfl - L/home/kundapur/GLIB- 2.12.9/lib - lglib- 2.0 - L/usr/local/lib - levtlog - lwrap - Wl,- Bdynamic
Here you're trying to build against a static glib- 2.0
$ cat glib.c # include <glib.h>
int main ( void ) { printf ( "glib version = %d.%d.%d\n", glib_major_version, glib_minor_version, glib_micro_version );
return 0; } $ cc glib.c `pkg- config -- cflags -- libs glib- 2.0` $ a.out glib version = 2.12.9
While this might be a dynamically linked executable. So I suppose you're missing the static glib library.
Regards,
Sandor --------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. _______________________________________________ syslog- ng maillist - syslog- ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog- ng Frequently asked questions at http://www.campin.net/syslog- ng/faq.html
On Tue, 17 Jul 2007 17:24:14 +0530, Ganesh Kundapur said:
gcc -g -O2 -Wall -g -o syslog-ng main.o libsyslog-ng.a -lnsl -lrt -Wl,-Bstatic -lfl -L/home/kundapur/GLIB-2.12.9/lib -lglib-2.0 -L/usr/local/lib -levtlog -lwrap -Wl,-Bdynamic
$ cc glib.c `pkg-config --cflags --libs glib-2.0`
This is a good way to shoot yourself in the foot - you're hand-specifying -L and -l flags in the first, but using pkgconfig to get the values in the second. If they ever get out of sync (because you actually installed into /opt/lib or whatever), you'll be banging your head against the wall for quite some time....
Q:Does the open source edition of syslog-ng support secure logging .. I mean does it support secure communication between logging hosts and the central log server running syslog-ng.. Thanks -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Valdis.Kletnieks@vt.edu Sent: Tuesday, July 17, 2007 11:59 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] syslog-ng-2.0.4 compilation error On Tue, 17 Jul 2007 17:24:14 +0530, Ganesh Kundapur said:
gcc -g -O2 -Wall -g -o syslog-ng main.o libsyslog-ng.a -lnsl -lrt -Wl,-Bstatic -lfl -L/home/kundapur/GLIB-2.12.9/lib -lglib-2.0 -L/usr/local/lib -levtlog -lwrap -Wl,-Bdynamic
$ cc glib.c `pkg-config --cflags --libs glib-2.0`
This is a good way to shoot yourself in the foot - you're hand-specifying -L and -l flags in the first, but using pkgconfig to get the values in the second. If they ever get out of sync (because you actually installed into /opt/lib or whatever), you'll be banging your head against the wall for quite some time....
Hi,
Q:Does the open source edition of syslog-ng support secure logging .. I mean does it support secure communication between logging hosts and the central log server running syslog-ng..
One major difference between the open-source and the premium version is encryption support, so the obvious answer is no. Regards, Sandor -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
On Tue, 2007-07-17 at 17:34 +0100, Geller, Sandor (IT) wrote:
Hi,
Q:Does the open source edition of syslog-ng support secure logging .. I mean does it support secure communication between logging hosts and the central log server running syslog-ng..
One major difference between the open-source and the premium version is encryption support, so the obvious answer is no.
the less obvious answer is that it can be integrated to use stunnel or other similar package. -- Bazsi
participants (6)
-
anthony lineham
-
Balazs Scheidler
-
Ganesh Kundapur
-
Geller, Sandor (IT)
-
Tamer Tayea
-
Valdis.Kletnieks＠vt.edu