[patch] Fix build with --disable-ssl
Hi, Here's a patch to fix building without SSL. Without it, tlstransport.h is included by tlstransport.c and things break because SSLisms are undefined. Thanks, Joe
This seems to do the trick, of course I'm on to something new now: gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -static -lrt -lnsl -lfl -L/usr/local/lib -lglib-2.0 -L/usr/local/lib -levtlog -ldl -lwrap -lcap /usr/bin/ld: cannot find -lcap collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/fabric/syslog-ng-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/fabric/syslog-ng-3.0.1' make: *** [all] Error 2 Upgrading to syslog-ng 2 on this same box wasn't this hard. :) chris On Mon, Jan 26, 2009 at 4:39 PM, Joe Shaw <joe@joeshaw.org> wrote:
Hi,
Here's a patch to fix building without SSL. Without it, tlstransport.h is included by tlstransport.c and things break because SSLisms are undefined.
Thanks, Joe
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
Hi, On Mon, Jan 26, 2009 at 6:23 PM, Chris Fabri <fabric@northwestern.edu> wrote:
This seems to do the trick, of course I'm on to something new now:
gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -static -lrt -lnsl -lfl -L/usr/local/lib -lglib-2.0 -L/usr/local/lib -levtlog -ldl -lwrap -lcap /usr/bin/ld: cannot find -lcap collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/fabric/syslog-ng-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/fabric/syslog-ng-3.0.1' make: *** [all] Error 2
Heh, are you running this on Fedora Core 3? I had the same problem -- basically, syslog-ng wants to link against a statically linked libpcap, but your system doesn't provide it. You need to do some tweaking of ordering of the libraries in configure.in to link against it dynamically. I can send you a patch when I get back to work tomorrow. Joe
On Mon, Jan 26, 2009 at 7:13 PM, Joe Shaw <joe@joeshaw.org> wrote:
Hi,
On Mon, Jan 26, 2009 at 6:23 PM, Chris Fabri <fabric@northwestern.edu> wrote:
This seems to do the trick, of course I'm on to something new now:
gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -static -lrt -lnsl -lfl -L/usr/local/lib -lglib-2.0 -L/usr/local/lib -levtlog -ldl -lwrap -lcap /usr/bin/ld: cannot find -lcap collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/fabric/syslog-ng-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/fabric/syslog-ng-3.0.1' make: *** [all] Error 2
Heh, are you running this on Fedora Core 3? I had the same problem -- basically, syslog-ng wants to link against a statically linked libpcap, but your system doesn't provide it. You need to do some tweaking of ordering of the libraries in configure.in to link against it dynamically. I can send you a patch when I get back to work tomorrow.
Joe ____
Joe- Yes, I'm on Fedora 3 unfortunately with this. Sorry to be a pest. I'm still banging my head against this, and if you could provide the patch for this I'm hoping this will get me through to a successful compile. Somebody had suggessted just disabling linux-cap, but that gives me a whole slew of new errors. chris
Hi, On Mon, Feb 2, 2009 at 3:33 PM, Chris Fabri <fabric@northwestern.edu> wrote:
Sorry to be a pest. I'm still banging my head against this, and if you could provide the patch for this I'm hoping this will get me through to a successful compile. Somebody had suggessted just disabling linux-cap, but that gives me a whole slew of new errors.
Oops, sorry, I forgot to send this out earlier. The patch is attached. It's to the configure.in, so you'll need to rerun autogen.sh after applying this. Joe
2009/2/2 Joe Shaw <joe@joeshaw.org>:
Oops, sorry, I forgot to send this out earlier.
The patch is attached. It's to the configure.in, so you'll need to rerun autogen.sh after applying this.
Joe
Joe- The attachment was for tlstransport.c, not to the configure.in. chris
On Tue, Feb 3, 2009 at 2:01 PM, Chris Fabri <fabric@northwestern.edu> wrote:
2009/2/2 Joe Shaw <joe@joeshaw.org>:
Oops, sorry, I forgot to send this out earlier.
The patch is attached. It's to the configure.in, so you'll need to rerun autogen.sh after applying this.
Joe
Joe-
The attachment was for tlstransport.c, not to the configure.in. chris
Joe- Hadn't heard anything back, I may not have been totally clear above. Based on what you wrote, I was expecting a patch for configure.in, not for tlstranport.c, which was what you had attached. That patch I had already applied, so I'm hoping there actually is something for configure.in that might help me out. :) chris
Hi, On Mon, Feb 9, 2009 at 10:50 AM, Chris Fabri <fabric@northwestern.edu> wrote:
Hadn't heard anything back, I may not have been totally clear above. Based on what you wrote, I was expecting a patch for configure.in, not for tlstranport.c, which was what you had attached. That patch I had already applied, so I'm hoping there actually is something for configure.in that might help me out. :) chris
My last email (from Feb 2) had a patch for configure.in. Basically you need to find the assignment of DEPS_LIBS and move $LIBCAP_LIBS outside of $LD_END_STATIC. Joe
On Mon, 2009-01-26 at 17:23 -0600, Chris Fabri wrote:
This seems to do the trick, of course I'm on to something new now:
gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -static -lrt -lnsl -lfl -L/usr/local/lib -lglib-2.0 -L/usr/local/lib -levtlog -ldl -lwrap -lcap /usr/bin/ld: cannot find -lcap collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/fabric/syslog-ng-3.0.1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/fabric/syslog-ng-3.0.1' make: *** [all] Error 2
Upgrading to syslog-ng 2 on this same box wasn't this hard. :) chris
libcap is part of the linux capability support. you can disable that as well, even though your headers seem to be installed, otherwise the configure script would have disabled it. maybe you only have a dynamic libcap, but not a static one? -- Bazsi
participants (3)
-
Balazs Scheidler
-
Chris Fabri
-
Joe Shaw