md5sum or sha1sum files not found .
Hello All , When going to ... http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.0.4/s... I am not finding either a md5sum or sha1sum (or greater) file for the contents . Is this due to decission not to or a oversight ? Tia , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
these are published on the download page, in the HTML page, here: http://www.balabit.com/network-security/syslog-ng/opensource-logging-system/... If you select "OS independent" that means source code, you can find the sha1sum there. On Sat, 2009-11-14 at 19:28 -0900, Mr. James W. Laferriere wrote:
Hello All , When going to ...
http://www.balabit.com/downloads/files/syslog-ng/open-source-edition/3.0.4/s...
I am not finding either a md5sum or sha1sum (or greater) file for the contents . Is this due to decission not to or a oversight ?
Tia , JimL
-- Bazsi
Hello All , Having just ran thru all of the changelogs I could find there is no mention of the change to requiring glib-2.10(or greater) except when running './configure' ie: " checking for GLIB - version >= 2.10.1... no *** Could not run GLIB test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GLIB is incorrectly installed. configure: error: Cannot find GLIB version >= 2.10.1: is pkg-config in path? " My system is quite old (ie: slackware 10.2 Circa 2005 , tho faithfully kept upto date for bug releases & such . There is no a graceful way to update to a newer glib . I was unable to find a reasonably 'Searchable' archive of the maillist or I'd have done that too . I have found that the requirement for glib-2.10 must go back as far as 2.0.3 as my local archive has mentions of glib-2.10 difficulties with that version of syslog-ng . so I guess it's back to 2.0.2 , Tho I am still not sure if even that will build . Thus my question , What is the last syslog-ng version that compiles under glibc-2.3.5 ? And will it be secure to run ? Tia , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
On Friday 27 of November 2009, Mr. James W. Laferriere wrote:
Hello All , Having just ran thru all of the changelogs I could find there is no mention of the change to requiring glib-2.10(or greater) except when running './configure' ie: " checking for GLIB - version >= 2.10.1... no [...]
My system is quite old (ie: slackware 10.2 Circa 2005 , tho faithfully kept upto date for bug releases & such . There is no a graceful way to update to a newer glib .
Try upgrading to glib2 (see below) from Slackware 11.0 (which has 2.10.3).
Thus my question , What is the last syslog-ng version that compiles under glibc-2.3.5 ? And will it be secure to run ?
Do not confuse "the C library" (glibc) with GLib. Versions 2.x of the latter are packaged as "glib2" in Slackware Linux. HTH -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D
Hello Jakub (& all) , On Fri, 27 Nov 2009, Jakub Jankowski wrote:
On Friday 27 of November 2009, Mr. James W. Laferriere wrote:
Hello All , Having just ran thru all of the changelogs I could find there is no mention of the change to requiring glib-2.10(or greater) except when running './configure' ie: " checking for GLIB - version >= 2.10.1... no [...]
My system is quite old (ie: slackware 10.2 Circa 2005 , tho faithfully kept upto date for bug releases & such . There is no a graceful way to update to a newer glib .
Try upgrading to glib2 (see below) from Slackware 11.0 (which has 2.10.3).
Thus my question , What is the last syslog-ng version that compiles under glibc-2.3.5 ? And will it be secure to run ?
Do not confuse "the C library" (glibc) with GLib. Versions 2.x of the latter are packaged as "glib2" in Slackware Linux. HTH That seemed to get me past that 'configure' difficulty , But of course there is now another during 'make' :-( . What include file am I missing now ? This is surely symptomatic of a missing include file or include file version level . I've searched the whole of my logging system & not found any .h file with this symbol defined on it . This is getting disheartening . Eventlog compiled w/o any problems at all .
The complete log (from off the Console) includes ./configure & make output , is available at : http://www.baby-dragons.com/syslog-ng-build-problems/syslog-ng-3.0.4_make.lo... if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT logmatcher.o -MD -MP -MF ".deps/logmatcher.Tpo" -c -o logmatcher.o logmatcher.c; \ then mv -f ".deps/logmatcher.Tpo" ".deps/logmatcher.Po"; else rm -f ".deps/logmatcher.Tpo"; exit 1; fi logmatcher.c: In function `log_matcher_pcre_re_compile': logmatcher.c:534: error: `PCRE_NEWLINE_ANYCRLF' undeclared (first use in this function) logmatcher.c:534: error: (Each undeclared identifier is reported only once logmatcher.c:534: error: for each function it appears in.) make[2]: *** [logmatcher.o] Error 1 make[2]: Leaving directory `/home/archive/syslog-ng-3.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/archive/syslog-ng-3.0.4' make: *** [all] Error 2 Tia , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
On Saturday 28 of November 2009, Mr. James W. Laferriere wrote:
That seemed to get me past that 'configure' difficulty , But of course there is now another during 'make' :-( . What include file am I missing now ? This is surely symptomatic of a missing include file or include file version level . I've searched the whole of my logging system & not found any .h file with this symbol defined on it . This is getting disheartening . Eventlog compiled w/o any problems at all . [...] logmatcher.c: In function `log_matcher_pcre_re_compile': logmatcher.c:534: error: `PCRE_NEWLINE_ANYCRLF' undeclared (first use in this function)
Your pcre is probably too old. Either compile with --disable-pcre, or upgrade pcre. HTH -- Jakub Jankowski|shasta@toxcorp.com|http://toxcorp.com/ GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D
Hello Jakub , On Sat, 28 Nov 2009, Jakub Jankowski wrote:
On Saturday 28 of November 2009, Mr. James W. Laferriere wrote:
That seemed to get me past that 'configure' difficulty , But of course there is now another during 'make' :-( . What include file am I missing now ? This is surely symptomatic of a missing include file or include file version level . I've searched the whole of my logging system & not found any .h file with this symbol defined on it . This is getting disheartening . Eventlog compiled w/o any problems at all . [...] logmatcher.c: In function `log_matcher_pcre_re_compile': logmatcher.c:534: error: `PCRE_NEWLINE_ANYCRLF' undeclared (first use in this function)
Your pcre is probably too old. Either compile with --disable-pcre, or upgrade pcre. HTH Yes it did help . But again another symbol is missing . This one seems to be in the tls libraries .
I'd like to suggest that the maintainer of the configure.in start checking for these symbols or AT LEAST the appropriate versions of the libraries these symbols reside in . The checking is obviosly not being done correctly or completely . As both of these symbols have been caught during compile time not during the checking that configure does . Also Please remember not every system out there is able to be deeply upgraded at many of its library levels . I remember having to dig out missing symbols back when I managed a Ultrix system (on a uVax) trying to get pppd and tools to compile . And just about any other tool I wanted on that system . But heck that was back in 1990 (and a little later) . Then a little bit after that as Linux began being the one OS I tended to lean toward . But most packages have progressed very nicely since then & I have not had to even think about these types of difficulties in some many years . But I do have to admit this system needs a to the roots upgrade . Which I am working toward , But even that's getting a tad slowed down . Sorry about the rant . Please take that suggestion to heart tho . Twyl , JimL if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT main.o -MD -MP -MF ".deps/main.Tpo" -c -o main.o main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f ".deps/main.Tpo"; exit 1; fi gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -lrt -lnsl -lfl -lglib-2.0 -L/usr/local/lib -levtlog -lssl -lcrypto -lz libsyslog-ng.a(tlscontext.o)(.text+0x6ea): In function `tls_context_setup_session': /home/archive/syslog-ng-3.0.4/src/tlscontext.c:278: undefined reference to `X509_VERIFY_PARAM_set_flags' collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/archive/syslog-ng-3.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/archive/syslog-ng-3.0.4' make: *** [all] Error 2 -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
Hello All (& Jakub if he's interested) , On Sat, 28 Nov 2009, Mr. James W. Laferriere wrote:
On Sat, 28 Nov 2009, Jakub Jankowski wrote:
On Saturday 28 of November 2009, Mr. James W. Laferriere wrote:
That seemed to get me past that 'configure' difficulty , But of course there is now another during 'make' :-( . What include file am I missing now ? This is surely symptomatic of a missing include file or include file version level . I've searched the whole of my logging system & not found any .h file with this symbol defined on it . This is getting disheartening . Eventlog compiled w/o any problems at all . [...] logmatcher.c: In function `log_matcher_pcre_re_compile': logmatcher.c:534: error: `PCRE_NEWLINE_ANYCRLF' undeclared (first use in this function)
Your pcre is probably too old. Either compile with --disable-pcre, or upgrade pcre. HTH Yes it did help . But again another symbol is missing . This one seems to be in the tls libraries .
I'd like to suggest that the maintainer of the configure.in start checking for these symbols or AT LEAST the appropriate versions of the libraries these symbols reside in . The checking is obviosly not being done correctly or completely . As both of these symbols have been caught during compile time not during the checking that configure does .
Also Please remember not every system out there is able to be deeply upgraded at many of its library levels .
I remember having to dig out missing symbols back when I managed a Ultrix system (on a uVax) trying to get pppd and tools to compile . And just about any other tool I wanted on that system . But heck that was back in 1990 (and a little later) . Then a little bit after that as Linux began being the one OS I tended to lean toward . But most packages have progressed very nicely since then & I have not had to even think about these types of difficulties in some many years .
But I do have to admit this system needs a to the roots upgrade . Which I am working toward , But even that's getting a tad slowed down . Sorry about the rant . Please take that suggestion to heart tho .
Twyl , JimL
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT main.o -MD -MP -MF ".deps/main.Tpo" -c -o main.o main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f ".deps/main.Tpo"; exit 1; fi gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -lrt -lnsl -lfl -lglib-2.0 -L/usr/local/lib -levtlog -lssl -lcrypto -lz libsyslog-ng.a(tlscontext.o)(.text+0x6ea): In function `tls_context_setup_session': /home/archive/syslog-ng-3.0.4/src/tlscontext.c:278: undefined reference to `X509_VERIFY_PARAM_set_flags' collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/archive/syslog-ng-3.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/archive/syslog-ng-3.0.4' make: *** [all] Error 2
Now I am confused , There is a .h file with the necessary symbol definition on my system & configure did not use that include file obviously . Unless there is something in the ld commands that forces the use of a *.so|*.a file instead (something like '-Bdynamic, -dy, -call_shared' ... ? I had just finished updating openssl (several days ago) & running ldconfig as well afterward in order to re-compile my ssh . # dir /usr/include/openssl/x509_vfy.h 24 -rw-r--r-- 1 root root 20782 2009-11-22 12:05 /usr/include/openssl/x509_vfy.h Lets see what the symbols definition looks like . # grep -C1 X509_VERIFY_PARAM_set_flags /usr/include/openssl/x509_vfy.h int X509_VERIFY_PARAM_set1_name(X509_VERIFY_PARAM *param, const char *name); :int X509_VERIFY_PARAM_set_flags(X509_VERIFY_PARAM *param, unsigned long flags); int X509_VERIFY_PARAM_clear_flags(X509_VERIFY_PARAM *param, Just in case there are more than one installed instance of openssl , It could have been hiding in /usr/local or some such , like I said this is an old box . # find / -xdev -name x509_vfy.h -ls 3565418 24 -rw-r--r-- 1 root root 20782 Nov 22 12:05 /usr/include/openssl/x509_vfy.h ./configure 2>&1 | tee syslog-ng-3.0.4_make.log make 2>&1 | tee -a syslog-ng-3.0.4_make.log The lastest of the above file is available if needed at http://www.baby-dragons.com/syslog-ng-build-problems/syslog-ng-3.0.4_make.lo... $ cat /etc/slackware-version Slackware 10.2.0 $ /usr/src/linux/scripts/ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux filesrv1 2.6.30.6 #2 SMP Tue Sep 15 22:45:28 AKDT 2009 i686 unknown unknown GNU/Linux Gnu C 3.3.6 Gnu make 3.80 binutils 2.15.92.0.2 util-linux 2.12p mount 2.12p module-init-tools 3.1 e2fsprogs 1.38 jfsutils 1.1.8 reiserfsprogs 3.6.19 xfsprogs 2.6.13 pcmcia-cs 3.2.8 quota-tools 3.12. PPP 2.4.4b1 nfs-utils 1.0.7 Linux C Library 2.3.5 Dynamic linker (ldd) 2.3.5 Linux C++ Library 5.0.7 Procps 3.2.5 Net-tools 1.60 Kbd 1.12 oprofile 0.9.1 Sh-utils 5.2.1 udev 064 Modules Loaded Tia , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
On Sat, 2009-11-28 at 19:03 -0900, Mr. James W. Laferriere wrote:
Hello All (& Jakub if he's interested) ,
On Sat, 28 Nov 2009, Mr. James W. Laferriere wrote:
On Sat, 28 Nov 2009, Jakub Jankowski wrote:
On Saturday 28 of November 2009, Mr. James W. Laferriere wrote:
That seemed to get me past that 'configure' difficulty , But of course there is now another during 'make' :-( . What include file am I missing now ? This is surely symptomatic of a missing include file or include file version level . I've searched the whole of my logging system & not found any .h file with this symbol defined on it . This is getting disheartening . Eventlog compiled w/o any problems at all . [...] logmatcher.c: In function `log_matcher_pcre_re_compile': logmatcher.c:534: error: `PCRE_NEWLINE_ANYCRLF' undeclared (first use in this function)
Your pcre is probably too old. Either compile with --disable-pcre, or upgrade pcre. HTH Yes it did help . But again another symbol is missing . This one seems to be in the tls libraries .
I'd like to suggest that the maintainer of the configure.in start checking for these symbols or AT LEAST the appropriate versions of the libraries these symbols reside in . The checking is obviosly not being done correctly or completely . As both of these symbols have been caught during compile time not during the checking that configure does .
Also Please remember not every system out there is able to be deeply upgraded at many of its library levels .
I remember having to dig out missing symbols back when I managed a Ultrix system (on a uVax) trying to get pppd and tools to compile . And just about any other tool I wanted on that system . But heck that was back in 1990 (and a little later) . Then a little bit after that as Linux began being the one OS I tended to lean toward . But most packages have progressed very nicely since then & I have not had to even think about these types of difficulties in some many years .
But I do have to admit this system needs a to the roots upgrade . Which I am working toward , But even that's getting a tad slowed down . Sorry about the rant . Please take that suggestion to heart tho .
Twyl , JimL
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT main.o -MD -MP -MF ".deps/main.Tpo" -c -o main.o main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f ".deps/main.Tpo"; exit 1; fi gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -lrt -lnsl -lfl -lglib-2.0 -L/usr/local/lib -levtlog -lssl -lcrypto -lz libsyslog-ng.a(tlscontext.o)(.text+0x6ea): In function `tls_context_setup_session': /home/archive/syslog-ng-3.0.4/src/tlscontext.c:278: undefined reference to `X509_VERIFY_PARAM_set_flags' collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/archive/syslog-ng-3.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/archive/syslog-ng-3.0.4' make: *** [all] Error 2
Now I am confused , There is a .h file with the necessary symbol definition on my system & configure did not use that include file obviously . Unless there is something in the ld commands that forces the use of a *.so|*.a file instead (something like '-Bdynamic, -dy, -call_shared' ... ?
I had just finished updating openssl (several days ago) & running ldconfig as well afterward in order to re-compile my ssh .
# dir /usr/include/openssl/x509_vfy.h 24 -rw-r--r-- 1 root root 20782 2009-11-22 12:05 /usr/include/openssl/x509_vfy.h
Lets see what the symbols definition looks like .
# grep -C1 X509_VERIFY_PARAM_set_flags /usr/include/openssl/x509_vfy.h
int X509_VERIFY_PARAM_set1_name(X509_VERIFY_PARAM *param, const char *name); :int X509_VERIFY_PARAM_set_flags(X509_VERIFY_PARAM *param, unsigned long flags); int X509_VERIFY_PARAM_clear_flags(X509_VERIFY_PARAM *param,
Just in case there are more than one installed instance of openssl , It could have been hiding in /usr/local or some such , like I said this is an old box .
# find / -xdev -name x509_vfy.h -ls
3565418 24 -rw-r--r-- 1 root root 20782 Nov 22 12:05 /usr/include/openssl/x509_vfy.h
What you get is a linker error, whereas the header file is used only by the compiler. So you seem to have an .so file that doesn't match your headers. X095_VERIFY_PARAM_set_flags() is defined by openssl 0.9.8 and syslog-ng is explicitly depending on 0.9.8. You probably also have 0.9.7 as well and for some reason the linker finds that. Regarding the rant, you're right that compiling a package from source with a lot of external dependencies is not and has never been easy. Especially if your build host has hacks and mismatching headers/libraries. However you could always try to install syslog-ng binaries, which you can find on BalaBit's homepage at: https://www.balabit.com/network-security/syslog-ng/opensource-logging-system... Click on the "Downloads" tab, then "Sources & binaries" We don't support these binaries on Slackware, however even if the install.sh script fails, you could always extract the binaries using ./syslog-ng<version>.run --tar xvfz then copy the binaries to /opt/syslog-ng and doing the necessary steps to disable syslogd & start syslog-ng in the boot process.
./configure 2>&1 | tee syslog-ng-3.0.4_make.log make 2>&1 | tee -a syslog-ng-3.0.4_make.log
The lastest of the above file is available if needed at http://www.baby-dragons.com/syslog-ng-build-problems/syslog-ng-3.0.4_make.lo...
$ cat /etc/slackware-version Slackware 10.2.0
-- Bazsi
Hello Balazs , On Sun, 29 Nov 2009, Balazs Scheidler wrote:
On Sat, 2009-11-28 at 19:03 -0900, Mr. James W. Laferriere wrote:
Hello All (& Jakub if he's interested) ,
On Sat, 28 Nov 2009, Mr. James W. Laferriere wrote:
On Sat, 28 Nov 2009, Jakub Jankowski wrote:
On Saturday 28 of November 2009, Mr. James W. Laferriere wrote:
That seemed to get me past that 'configure' difficulty , But of course there is now another during 'make' :-( . What include file am I missing now ? This is surely symptomatic of a missing include file or include file version level . I've searched the whole of my logging system & not found any .h file with this symbol defined on it . This is getting disheartening . Eventlog compiled w/o any problems at all . [...] logmatcher.c: In function `log_matcher_pcre_re_compile': logmatcher.c:534: error: `PCRE_NEWLINE_ANYCRLF' undeclared (first use in this function)
Your pcre is probably too old. Either compile with --disable-pcre, or upgrade pcre. HTH Yes it did help . But again another symbol is missing . This one seems to be in the tls libraries .
I'd like to suggest that the maintainer of the configure.in start checking for these symbols or AT LEAST the appropriate versions of the libraries these symbols reside in . The checking is obviosly not being done correctly or completely . As both of these symbols have been caught during compile time not during the checking that configure does .
Also Please remember not every system out there is able to be deeply upgraded at many of its library levels .
I remember having to dig out missing symbols back when I managed a Ultrix system (on a uVax) trying to get pppd and tools to compile . And just about any other tool I wanted on that system . But heck that was back in 1990 (and a little later) . Then a little bit after that as Linux began being the one OS I tended to lean toward . But most packages have progressed very nicely since then & I have not had to even think about these types of difficulties in some many years .
But I do have to admit this system needs a to the roots upgrade . Which I am working toward , But even that's getting a tad slowed down . Sorry about the rant . Please take that suggestion to heart tho .
Twyl , JimL
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT main.o -MD -MP -MF ".deps/main.Tpo" -c -o main.o main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f ".deps/main.Tpo"; exit 1; fi gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -lrt -lnsl -lfl -lglib-2.0 -L/usr/local/lib -levtlog -lssl -lcrypto -lz libsyslog-ng.a(tlscontext.o)(.text+0x6ea): In function `tls_context_setup_session': /home/archive/syslog-ng-3.0.4/src/tlscontext.c:278: undefined reference to `X509_VERIFY_PARAM_set_flags' collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/archive/syslog-ng-3.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/archive/syslog-ng-3.0.4' make: *** [all] Error 2
Now I am confused , There is a .h file with the necessary symbol definition on my system & configure did not use that include file obviously . Unless there is something in the ld commands that forces the use of a *.so|*.a file instead (something like '-Bdynamic, -dy, -call_shared' ... ?
I had just finished updating openssl (several days ago) & running ldconfig as well afterward in order to re-compile my ssh .
# dir /usr/include/openssl/x509_vfy.h 24 -rw-r--r-- 1 root root 20782 2009-11-22 12:05 /usr/include/openssl/x509_vfy.h
Lets see what the symbols definition looks like .
# grep -C1 X509_VERIFY_PARAM_set_flags /usr/include/openssl/x509_vfy.h
int X509_VERIFY_PARAM_set1_name(X509_VERIFY_PARAM *param, const char *name); :int X509_VERIFY_PARAM_set_flags(X509_VERIFY_PARAM *param, unsigned long flags); int X509_VERIFY_PARAM_clear_flags(X509_VERIFY_PARAM *param,
Just in case there are more than one installed instance of openssl , It could have been hiding in /usr/local or some such , like I said this is an old box .
# find / -xdev -name x509_vfy.h -ls
3565418 24 -rw-r--r-- 1 root root 20782 Nov 22 12:05 /usr/include/openssl/x509_vfy.h
What you get is a linker error, whereas the header file is used only by the compiler. So you seem to have an .so file that doesn't match your headers.
X095_VERIFY_PARAM_set_flags() is defined by openssl 0.9.8 and syslog-ng is explicitly depending on 0.9.8. You probably also have 0.9.7 as well and for some reason the linker finds that. That hit the nail on the head (& mine) . (*) ie: /usr/lib/openssl.so.0 -> openssl.so.0.9.7 re linked to openssl.so.0.9.8 And all compiled fine . Updated pcre to minimum needed just prior .
Regarding the rant, you're right that compiling a package from source with a lot of external dependencies is not and has never been easy. Especially if your build host has hacks and mismatching headers/libraries. Still checking for the minimum required libraries in configure.in is quite doable & someone missed the possibility of the above (*) and it did not get caught . Not to mention the operator (me) didn't either :^( .
However you could always try to install syslog-ng binaries, which you can find on BalaBit's homepage at:
https://www.balabit.com/network-security/syslog-ng/opensource-logging-system...
Click on the "Downloads" tab, then "Sources & binaries"
We don't support these binaries on Slackware, however even if the install.sh script fails, you could always extract the binaries using
./syslog-ng<version>.run --tar xvfz
then copy the binaries to /opt/syslog-ng and doing the necessary steps to disable syslogd & start syslog-ng in the boot process. Beleive me I am aware that balabit does not support slackware packages . And the only way i could use those packaged binaries is if they were statically linked . But I've gotten things straightened enough that syslog-ng-3.0.4 now compiles succssfully , not saying that the binary I've created is usable but ... I'll give this a try and go from there .
With thanks to Jakub & Balazs . Twyl , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
On Sun, 2009-11-29 at 18:31 -0900, Mr. James W. Laferriere wrote:
Hello Balazs ,
On Sun, 29 Nov 2009, Balazs Scheidler wrote:
On Sat, 2009-11-28 at 19:03 -0900, Mr. James W. Laferriere wrote:
Hello All (& Jakub if he's interested) ,
On Sat, 28 Nov 2009, Mr. James W. Laferriere wrote:
On Sat, 28 Nov 2009, Jakub Jankowski wrote:
On Saturday 28 of November 2009, Mr. James W. Laferriere wrote:
That seemed to get me past that 'configure' difficulty , But of course there is now another during 'make' :-( . What include file am I missing now ? This is surely symptomatic of a missing include file or include file version level . I've searched the whole of my logging system & not found any .h file with this symbol defined on it . This is getting disheartening . Eventlog compiled w/o any problems at all . [...] logmatcher.c: In function `log_matcher_pcre_re_compile': logmatcher.c:534: error: `PCRE_NEWLINE_ANYCRLF' undeclared (first use in this function)
Your pcre is probably too old. Either compile with --disable-pcre, or upgrade pcre. HTH Yes it did help . But again another symbol is missing . This one seems to be in the tls libraries .
I'd like to suggest that the maintainer of the configure.in start checking for these symbols or AT LEAST the appropriate versions of the libraries these symbols reside in . The checking is obviosly not being done correctly or completely . As both of these symbols have been caught during compile time not during the checking that configure does .
Also Please remember not every system out there is able to be deeply upgraded at many of its library levels .
I remember having to dig out missing symbols back when I managed a Ultrix system (on a uVax) trying to get pppd and tools to compile . And just about any other tool I wanted on that system . But heck that was back in 1990 (and a little later) . Then a little bit after that as Linux began being the one OS I tended to lean toward . But most packages have progressed very nicely since then & I have not had to even think about these types of difficulties in some many years .
But I do have to admit this system needs a to the roots upgrade . Which I am working toward , But even that's getting a tad slowed down . Sorry about the rant . Please take that suggestion to heart tho .
Twyl , JimL
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/local/include/eventlog -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -Wall -MT main.o -MD -MP -MF ".deps/main.Tpo" -c -o main.o main.c; \ then mv -f ".deps/main.Tpo" ".deps/main.Po"; else rm -f ".deps/main.Tpo"; exit 1; fi gcc -g -O2 -Wall -o syslog-ng main.o libsyslog-ng.a -lrt -lnsl -lfl -lglib-2.0 -L/usr/local/lib -levtlog -lssl -lcrypto -lz libsyslog-ng.a(tlscontext.o)(.text+0x6ea): In function `tls_context_setup_session': /home/archive/syslog-ng-3.0.4/src/tlscontext.c:278: undefined reference to `X509_VERIFY_PARAM_set_flags' collect2: ld returned 1 exit status make[2]: *** [syslog-ng] Error 1 make[2]: Leaving directory `/home/archive/syslog-ng-3.0.4/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/archive/syslog-ng-3.0.4' make: *** [all] Error 2
Now I am confused , There is a .h file with the necessary symbol definition on my system & configure did not use that include file obviously . Unless there is something in the ld commands that forces the use of a *.so|*.a file instead (something like '-Bdynamic, -dy, -call_shared' ... ?
I had just finished updating openssl (several days ago) & running ldconfig as well afterward in order to re-compile my ssh .
# dir /usr/include/openssl/x509_vfy.h 24 -rw-r--r-- 1 root root 20782 2009-11-22 12:05 /usr/include/openssl/x509_vfy.h
Lets see what the symbols definition looks like .
# grep -C1 X509_VERIFY_PARAM_set_flags /usr/include/openssl/x509_vfy.h
int X509_VERIFY_PARAM_set1_name(X509_VERIFY_PARAM *param, const char *name); :int X509_VERIFY_PARAM_set_flags(X509_VERIFY_PARAM *param, unsigned long flags); int X509_VERIFY_PARAM_clear_flags(X509_VERIFY_PARAM *param,
Just in case there are more than one installed instance of openssl , It could have been hiding in /usr/local or some such , like I said this is an old box .
# find / -xdev -name x509_vfy.h -ls
3565418 24 -rw-r--r-- 1 root root 20782 Nov 22 12:05 /usr/include/openssl/x509_vfy.h
What you get is a linker error, whereas the header file is used only by the compiler. So you seem to have an .so file that doesn't match your headers.
X095_VERIFY_PARAM_set_flags() is defined by openssl 0.9.8 and syslog-ng is explicitly depending on 0.9.8. You probably also have 0.9.7 as well and for some reason the linker finds that. That hit the nail on the head (& mine) . (*) ie: /usr/lib/openssl.so.0 -> openssl.so.0.9.7 re linked to openssl.so.0.9.8 And all compiled fine . Updated pcre to minimum needed just prior .
Regarding the rant, you're right that compiling a package from source with a lot of external dependencies is not and has never been easy. Especially if your build host has hacks and mismatching headers/libraries. Still checking for the minimum required libraries in configure.in is quite doable & someone missed the possibility of the above (*) and it did not get caught . Not to mention the operator (me) didn't either :^( .
In the openssl case, syslog-ng does check the version number: PKG_CHECK_MODULES(OPENSSL, openssl >= $OPENSSL_MIN_VERSION,, OPENSSL_LIBS="") OPENSSL_MIN_VERSION contains 0.9.8, however syslog-ng relies on the standard pkg-config mechanism, and doesn't attempt to link against the lib found this way. Regarding pcre, you're right, pcre version number checking is not there.
However you could always try to install syslog-ng binaries, which you can find on BalaBit's homepage at:
https://www.balabit.com/network-security/syslog-ng/opensource-logging-system...
Click on the "Downloads" tab, then "Sources & binaries"
We don't support these binaries on Slackware, however even if the install.sh script fails, you could always extract the binaries using
./syslog-ng<version>.run --tar xvfz
then copy the binaries to /opt/syslog-ng and doing the necessary steps to disable syslogd & start syslog-ng in the boot process. Beleive me I am aware that balabit does not support slackware packages . And the only way i could use those packaged binaries is if they were statically linked .
no, the package above includes _all_ necessary .so files to run syslog-ng, except for glibc. the reason we're linking dynamically against those .so files is that the GPL requires us to supply dynamically linked binaries against LGPL libraries, in order to make it possible to replace the .so file with a changed version. If you at least run on a glibc version that matches Debian sarge (where we compile our packages), you should be fine with the above binaries. sarge uses "2.3.6", so do we depend on that version.
But I've gotten things straightened enough that syslog-ng-3.0.4 now compiles succssfully , not saying that the binary I've created is usable but ... I'll give this a try and go from there .
-- Bazsi
Hi all, On Sun, Nov 29, 2009 at 06:31:06PM -0900, Mr. James W. Laferriere wrote:
X095_VERIFY_PARAM_set_flags() is defined by openssl 0.9.8 and syslog-ng is explicitly depending on 0.9.8. You probably also have 0.9.7 as well and for some reason the linker finds that. That hit the nail on the head (& mine) . (*) ie: /usr/lib/openssl.so.0 -> openssl.so.0.9.7 re linked to openssl.so.0.9.8 And all compiled fine . Updated pcre to minimum needed just prior . Something is funny here. configure (through pkg-config) checks if openssl's minimum version is 0.9.8. It's possible that pkg-config found an openssl.pc file wich said 0.9.8 but the libssl.so (which the linker uses) was pointed to libssl.so.0.9.7.
This is could be the problem when you install different versions of openssl under the same prefix(forex. 0.9.7 from slackware and 0.9.8 from source), because make install will overwrite files without hesitation.* Because of this, it's always recommended to install your custom packages to somewhere else than the distros default /usr/lib/ and use CFLAGS, LDFLAGS and/or configure's options to specify the version you want to use. * You can check this, by running 'pkg-config --modversion openssl' (which returns the version found in the openssl.pc file and 'pkg-config --cflags --libs openssl' which returns the needed compiler and linker flags. Mind you, pkg-config never checks anything else than the contents of the <modulename>.pc file. If the state of your system is different than the contents of the .pc files you will get mystical errors like this.
Regarding the rant, you're right that compiling a package from source with a lot of external dependencies is not and has never been easy. Especially if your build host has hacks and mismatching headers/libraries. Still checking for the minimum required libraries in configure.in is quite doable & someone missed the possibility of the above (*) and it did not get caught . Not to mention the operator (me) didn't either :^( .
We check for openssl 0.9.8 using pkg-config. The current check for pcre is not as sophisticated, only checking for the existence of the library (pcre didn't have support for pkg-config when syslog-ng started to use it) but we can update it now. Regards, -- Pal Tamas/Folti folti@balabit.hu
Regarding the rant, you're right that compiling a package from source with a lot of external dependencies is not and has never been easy. Especially if your build host has hacks and mismatching headers/libraries. Still checking for the minimum required libraries in configure.in is quite doable & someone missed the possibility of the above (*) and it did not get caught . Not to mention the operator (me) didn't either :^( .
Added pcre checking to 3.0.4 tree. I don't know when Bazsi will push it to the git.balabit.com repo: commit 2379efadb16946300cc46cae5637d983badaebb4 Author: Tamas Pal <folti@balabit.hu> Date: Mon Nov 30 13:27:48 2009 +0100 Added version checking for pcre. diff --git a/configure.in b/configure.in index 66b3b12..7f67167 100644 --- a/configure.in +++ b/configure.in @@ -24,6 +24,7 @@ GLIB_MIN_VERSION="2.10.1" EVTLOG_MIN_VERSION="0.2" OPENSSL_MIN_VERSION="0.9.8" LIBDBI_MIN_VERSION="0.8.0" +PCRE_MIN_VERSION="7.3" dnl *************************************************************************** dnl Initial setup @@ -294,7 +295,19 @@ if test "x$enable_linux_caps" = "xyes" -o "x$enable_linux_caps" = "xauto"; then AC_CHECK_LIB(cap, cap_set_proc, LIBCAP_LIBS="-lcap") fi if test "x$enable_pcre" = "xyes" -o "x$enable_pcre" = "xauto"; then - AC_CHECK_LIB(pcre, pcre_compile, PCRE_LIBS="-lpcre") + PKG_CHECK_MODULES(PCRE, libpcre >= $PCRE_MIN_VERSION,, PCRE_LIBS="") + if test -z "$PCRE_LIBS"; then + if test "x$enable_pcre" = "xyes"; then + AC_MSG_ERROR(Cannot find pcre version >= $PCRE_MIN_VERSION.) + else + AC_MSG_WARN(Cannot find pcre version >= $PCRE_MIN_VERSION. pcre support disabled.) + fi + fi +fi + +if test -z "$PCRE_LIBS"; then + PCRE_LIBS="" + PCRE_CFLAGS="" fi if test "x$enable_env_wrapper" = "xauto"; then @@ -497,7 +510,7 @@ fi if test "x$enable_pcre" = "xauto"; then AC_MSG_CHECKING(whether to enable PCRE support) - if test "x$ac_cv_lib_pcre_pcre_compile" = "xyes"; then + if test "x$PCRE_LIBS" != "x"; then enable_pcre="yes" else enable_pcre="no" -- Pal Tamas/Folti folti@balabit.hu
Hello All , when doing a 'make install' in eventlog-0.2.10 the file eventlog.pc is NOT installed to /usr/lib64 (see .configure below) . Thus when doing a ./configure in syslog-ng-3.0.5 the configure is unable to find the file on my x86_64 based system . Hopefully everything needed is below . root@ebf:~/syslog-ng_eventlog-0.2.10# ./configure --prefix=/usr \
--sysconfdir=/etc \ --libexecdir=/usr/libexec \ --localstatedir=/var \ --mandir=/usr/man --infodir=/usr/info \ --enable-debug --enable-dlsym-wrapper \ --enable-dependency-tracking checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/x86_64-slackware-linux/bin/ld checking if the linker (/usr/x86_64-slackware-linux/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/x86_64-slackware-linux/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for an ANSI C-conforming const... yes checking for strdup... yes checking for strerror... yes checking for dlsym in -ldl... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating tests/Makefile config.status: creating tgzbuild/Makefile config.status: creating tgz2build/Makefile config.status: creating eventlog.pc config.status: creating eventlog.spec.bb config.status: creating solbuild/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands root@ebf:~/syslog-ng_eventlog-0.2.10# make make all-recursive make[1]: Entering directory `/root/syslog-ng_eventlog-0.2.10' Making all in src make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/src' if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtrec.lo -MD -MP -MF ".deps/evtrec.Tpo" -c -o evtrec.lo evtrec.c; \ then mv -f ".deps/evtrec.Tpo" ".deps/evtrec.Plo"; else rm -f ".deps/evtrec.Tpo"; exit 1; fi libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtrec.lo -MD -MP -MF .deps/evtrec.Tpo -c evtrec.c -fPIC -DPIC -o .libs/evtrec.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtrec.lo -MD -MP -MF .deps/evtrec.Tpo -c evtrec.c -o evtrec.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtfmt.lo -MD -MP -MF ".deps/evtfmt.Tpo" -c -o evtfmt.lo evtfmt.c; \ then mv -f ".deps/evtfmt.Tpo" ".deps/evtfmt.Plo"; else rm -f ".deps/evtfmt.Tpo"; exit 1; fi libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtfmt.lo -MD -MP -MF .deps/evtfmt.Tpo -c evtfmt.c -fPIC -DPIC -o .libs/evtfmt.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtfmt.lo -MD -MP -MF .deps/evtfmt.Tpo -c evtfmt.c -o evtfmt.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtout.lo -MD -MP -MF ".deps/evtout.Tpo" -c -o evtout.lo evtout.c; \ then mv -f ".deps/evtout.Tpo" ".deps/evtout.Plo"; else rm -f ".deps/evtout.Tpo"; exit 1; fi libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtout.lo -MD -MP -MF .deps/evtout.Tpo -c evtout.c -fPIC -DPIC -o .libs/evtout.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtout.lo -MD -MP -MF .deps/evtout.Tpo -c evtout.c -o evtout.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtstr.lo -MD -MP -MF ".deps/evtstr.Tpo" -c -o evtstr.lo evtstr.c; \ then mv -f ".deps/evtstr.Tpo" ".deps/evtstr.Plo"; else rm -f ".deps/evtstr.Tpo"; exit 1; fi libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtstr.lo -MD -MP -MF .deps/evtstr.Tpo -c evtstr.c -fPIC -DPIC -o .libs/evtstr.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtstr.lo -MD -MP -MF .deps/evtstr.Tpo -c evtstr.c -o evtstr.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtctx.lo -MD -MP -MF ".deps/evtctx.Tpo" -c -o evtctx.lo evtctx.c; \ then mv -f ".deps/evtctx.Tpo" ".deps/evtctx.Plo"; else rm -f ".deps/evtctx.Tpo"; exit 1; fi libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtctx.lo -MD -MP -MF .deps/evtctx.Tpo -c evtctx.c -fPIC -DPIC -o .libs/evtctx.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtctx.lo -MD -MP -MF .deps/evtctx.Tpo -c evtctx.c -o evtctx.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evttags.lo -MD -MP -MF ".deps/evttags.Tpo" -c -o evttags.lo evttags.c; \ then mv -f ".deps/evttags.Tpo" ".deps/evttags.Plo"; else rm -f ".deps/evttags.Tpo"; exit 1; fi libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evttags.lo -MD -MP -MF .deps/evttags.Tpo -c evttags.c -fPIC -DPIC -o .libs/evttags.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evttags.lo -MD -MP -MF .deps/evttags.Tpo -c evttags.c -o evttags.o >/dev/null 2>&1 if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtsyslog.lo -MD -MP -MF ".deps/evtsyslog.Tpo" -c -o evtsyslog.lo evtsyslog.c; \ then mv -f ".deps/evtsyslog.Tpo" ".deps/evtsyslog.Plo"; else rm -f ".deps/evtsyslog.Tpo"; exit 1; fi libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtsyslog.lo -MD -MP -MF .deps/evtsyslog.Tpo -c evtsyslog.c -fPIC -DPIC -o .libs/evtsyslog.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I. -I.. -D_GNU_SOURCE -Wall -g -MT evtsyslog.lo -MD -MP -MF .deps/evtsyslog.Tpo -c evtsyslog.c -o evtsyslog.o /dev/null 2>&1 /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -g -o libevtlog.la -rpath /usr/lib evtrec.lo evtfmt.lo evtout.lo evtstr.lo evtctx.lo evttags.lo evtsyslog.lo -ldl libtool: link: gcc -shared .libs/evtrec.o .libs/evtfmt.o .libs/evtout.o .libs/evtstr.o .libs/evtctx.o .libs/evttags.o .libs/evtsyslog.o -ldl -Wl,-soname -Wl,libevtlog.so.0 -o .libs/libevtlog.so.0.0.0 libtool: link: (cd ".libs" && rm -f "libevtlog.so.0" && ln -s "libevtlog.so.0.0.0" "libevtlog.so.0") libtool: link: (cd ".libs" && rm -f "libevtlog.so" && ln -s "libevtlog.so.0.0.0" "libevtlog.so") libtool: link: ar cru .libs/libevtlog.a evtrec.o evtfmt.o evtout.o evtstr.o evtctx.o evttags.o evtsyslog.o libtool: link: ranlib .libs/libevtlog.a libtool: link: ( cd ".libs" && rm -f "libevtlog.la" && ln -s "../libevtlog.la" "libevtlog.la" ) make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/src' Making all in tests make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tests' if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -D_GNU_SOURCE -Wall -g -MT evtrec.o -MD -MP -MF ".deps/evtrec.Tpo" -c -o evtrec.o evtrec.c; \ then mv -f ".deps/evtrec.Tpo" ".deps/evtrec.Po"; else rm -f ".deps/evtrec.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -g -o evtrec evtrec.o ../src/libevtlog.la -ldl libtool: link: gcc -Wall -g -o .libs/evtrec evtrec.o ../src/.libs/libevtlog.so -ldl if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -D_GNU_SOURCE -Wall -g -MT evtfmt.o -MD -MP -MF ".deps/evtfmt.Tpo" -c -o evtfmt.o evtfmt.c; \ then mv -f ".deps/evtfmt.Tpo" ".deps/evtfmt.Po"; else rm -f ".deps/evtfmt.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -g -o evtfmt evtfmt.o ../src/libevtlog.la -ldl libtool: link: gcc -Wall -g -o .libs/evtfmt evtfmt.o ../src/.libs/libevtlog.so -ldl if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -D_GNU_SOURCE -Wall -g -MT evtsyslog.o -MD -MP -MF ".deps/evtsyslog.Tpo" -c -o evtsyslog.o evtsyslog.c; \ then mv -f ".deps/evtsyslog.Tpo" ".deps/evtsyslog.Po"; else rm -f ".deps/evtsyslog.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -g -o evtsyslog evtsyslog.o ../src/libevtlog.la -ldl libtool: link: gcc -Wall -g -o .libs/evtsyslog evtsyslog.o ../src/.libs/libevtlog.so -ldl if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -D_GNU_SOURCE -DEVENTLOG_SYSLOG_MACROS=1 -Wall -g -MT evtsyslog_macros-evtsyslog.o -MD -MP -MF ".deps/evtsyslog_macros-evtsyslog.Tpo" -c -o evtsyslog_macros-evtsyslog.o `test -f 'evtsyslog.c' || echo './'`evtsyslog.c; \ then mv -f ".deps/evtsyslog_macros-evtsyslog.Tpo" ".deps/evtsyslog_macros-evtsyslog.Po"; else rm -f ".deps/evtsyslog_macros-evtsyslog.Tpo"; exit 1; fi /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -g -o evtsyslog-macros evtsyslog_macros-evtsyslog.o ../src/libevtlog.la -ldl libtool: link: gcc -Wall -g -o .libs/evtsyslog-macros evtsyslog_macros-evtsyslog.o ../src/.libs/libevtlog.so -ldl make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tests' Making all in solbuild make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/solbuild' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/solbuild' Making all in tgzbuild make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tgzbuild' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tgzbuild' Making all in tgz2build make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tgz2build' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tgz2build' make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10' make[1]: Leaving directory `/root/syslog-ng_eventlog-0.2.10' root@ebf:~/syslog-ng_eventlog-0.2.10# make install Making install in src make[1]: Entering directory `/root/syslog-ng_eventlog-0.2.10/src' make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/src' test -z "/usr/lib" || mkdir -p -- "/usr/lib" /bin/sh ../libtool --mode=install /usr/bin/ginstall -c 'libevtlog.la' '/usr/lib/libevtlog.la' libtool: install: /usr/bin/ginstall -c .libs/libevtlog.so.0.0.0 /usr/lib/libevtlog.so.0.0.0 libtool: install: (cd /usr/lib && { ln -s -f libevtlog.so.0.0.0 libevtlog.so.0 || { rm -f libevtlog.so.0 && ln -s libevtlog.so.0.0.0 libevtlog.so.0; }; }) libtool: install: (cd /usr/lib && { ln -s -f libevtlog.so.0.0.0 libevtlog.so || { rm -f libevtlog.so && ln -s libevtlog.so.0.0.0 libevtlog.so; }; }) libtool: install: /usr/bin/ginstall -c .libs/libevtlog.lai /usr/lib/libevtlog.la libtool: install: /usr/bin/ginstall -c .libs/libevtlog.a /usr/lib/libevtlog.a libtool: install: chmod 644 /usr/lib/libevtlog.a libtool: install: ranlib /usr/lib/libevtlog.a libtool: finish: PATH="/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/java/bin:/usr/lib64/qt/bin:/usr/share/texmf/bin:/sbin" ldconfig -n /usr/lib
Libraries have been installed in: /usr/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,-rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- test -z "/usr/include/eventlog" || mkdir -p -- "/usr/include/eventlog" /usr/bin/ginstall -c -m 644 'evtmaps.h' '/usr/include/eventlog/evtmaps.h' /usr/bin/ginstall -c -m 644 'evtlog.h' '/usr/include/eventlog/evtlog.h' make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/src' make[1]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/src' Making install in tests make[1]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tests' make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tests' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tests' make[1]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tests' Making install in solbuild make[1]: Entering directory `/root/syslog-ng_eventlog-0.2.10/solbuild' make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/solbuild' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/solbuild' make[1]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/solbuild' Making install in tgzbuild make[1]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tgzbuild' make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tgzbuild' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tgzbuild' make[1]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tgzbuild' Making install in tgz2build make[1]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tgz2build' make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10/tgz2build' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tgz2build' make[1]: Leaving directory `/root/syslog-ng_eventlog-0.2.10/tgz2build' make[1]: Entering directory `/root/syslog-ng_eventlog-0.2.10' make[2]: Entering directory `/root/syslog-ng_eventlog-0.2.10' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/pkgconfig" || mkdir -p -- "/usr/lib/pkgconfig" /usr/bin/ginstall -c -m 644 'eventlog.pc' '/usr/lib/pkgconfig/eventlog.pc' make[2]: Leaving directory `/root/syslog-ng_eventlog-0.2.10' make[1]: Leaving directory `/root/syslog-ng_eventlog-0.2.10' root@ebf:~/syslog-ng_eventlog-0.2.10# cd ../syslog-ng syslog-ng-3.0.5/ syslog-ng_eventlog-0.2.10/ syslog-ng-3_0_5.tgz syslog-ng_eventlog-0_2_10.tgz syslog-ng-v3_0-guide-admin-en-20091106.pdf root@ebf:~/syslog-ng_eventlog-0.2.10# cd ../syslog-ng-3.0.5/ root@ebf:~/syslog-ng-3.0.5# make distclean make: *** No rule to make target `distclean'. Stop. root@ebf:~/syslog-ng-3.0.5# ./configure --prefix=/usr --sysconfdir=/etc \
--libexecdir=/usr/libexec \ --localstatedir=/var \ --mandir=/usr/man --infodir=/usr/info \ --enable-debug \ --enable-ssl \ --enable-tcp-wrapper \ --enable-spoof-source \ --enable-sql \ --enable-linux-caps \ --enable-pcre checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for bison... bison -y checking for flex... flex checking lex output file root... lex.yy checking lex library... -lfl checking whether yytext is a pointer... yes checking whether make sets $(MAKE)... (cached) yes checking for ranlib... ranlib checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking how to enable static linking for certain libraries... GNU or Solaris checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dmalloc.h usability... no checking dmalloc.h presence... no checking for dmalloc.h... no checking for strings.h... (cached) yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking stropts.h usability... yes checking stropts.h presence... yes checking for stropts.h... yes checking sys/strlog.h usability... no checking sys/strlog.h presence... no checking for sys/strlog.h... no checking door.h usability... no checking door.h presence... no checking for door.h... no checking sys/capability.h usability... yes checking sys/capability.h presence... yes checking for sys/capability.h... yes checking sys/prctl.h usability... yes checking sys/prctl.h presence... yes checking for sys/prctl.h... yes checking tcpd.h usability... yes checking tcpd.h presence... yes checking for tcpd.h... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for struct tm.tm_gmtoff... yes checking for I_CONSLOG... no checking for O_LARGEFILE... yes checking for struct sockaddr_storage... yes checking for struct sockaddr_in6... yes checking for PR_SET_KEEPCAPS... yes checking for door_create in -ldoor... no checking for socket in -lsocket... no checking for nanosleep in -lrt... yes checking for gethostbyname in -lnsl... yes checking for regexec in -lregex... no checking for res_init in -lresolv... no checking for cap_set_proc in -lcap... yes checking for PCRE... yes checking for strdup... yes checking for strtol... yes checking for strtoll... yes checking for strtoimax... yes checking for inet_aton... yes checking for inet_ntoa... yes checking for getopt_long... yes checking for getaddrinfo... yes checking for getutent... yes checking for pread... yes checking for pwrite... yes checking for strcasestr... yes checking for TCP wrapper library... checking for OPENSSL... yes checking for dlsym in -ldl... yes checking for inflate in -lz... yes checking for dlsym in -ldl... (cached) yes checking for LIBDBI... no checking for dbi_initialize in -ldbi... no checking for LIBNET... which: no libnet-config in (/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/java/bin:/usr/lib64/qt/bin:/usr/share/texmf/bin) no checking whether to enable Sun STREAMS support... no checking whether to enable Sun door support... no checking whether to enable IPv6 support... yes checking for pkg-config... (cached) /usr/bin/pkg-config checking pkg-config is at least version 0.14... yes checking for GLIB - version >= 2.10.1... yes (version 2.18.4) checking for EVTLOG... no configure: error: Cannot find eventlog version >= 0.2: is pkg-config in path?
Yes it sure is ... root@ebf:~/syslog-ng-3.0.5# pkg-config Must specify package names on the command line Distribution info ... # cat /etc/slackware-version Slackware 13.0.0.0.0 ver_linux output ... Linux ebf 2.6.32.3 #1 SMP Thu Jan 14 16:27:57 AKST 2010 x86_64 AMD Phenom(tm) 9950 Quad-Core Processor AuthenticAMD GNU/Linux Gnu C 4.3.3 Gnu make 3.81 binutils 2.18.50.0.9.20080822 util-linux 2.14.2 mount 2.14.2 (with libblkid support) module-init-tools 3.6 e2fsprogs 1.41.8 jfsutils 1.1.14 reiserfsprogs 3.6.21 xfsprogs 3.0.1 pcmciautils 015 quota-tools 3.17. PPP 2.4.4 Linux C Library 2.9 Dynamic linker (ldd) 2.9 Procps 3.2.7 Net-tools 1.60 Kbd 1.15 oprofile 0.9.4 Sh-utils 7.4 wireless-tools 29 Modules Loaded rtc_cmos rtc_core rtc_lib e1000 processor thermal shpchp thermal_sys ac i2c_piix4 button container hwmon intel_agp Any other info regarding this difficulty gladly provided for the asking . Hth , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
On Sun, Jan 17, 2010 at 6:29 PM, Mr. James W. Laferriere < babydr@baby-dragons.com> wrote:
Hello All , when doing a 'make install' in eventlog-0.2.10 the file eventlog.pc is NOT installed to /usr/lib64 (see .configure below) . Thus when doing a ./configure in syslog-ng-3.0.5 the configure is unable to find the file on my x86_64 based system . Hopefully everything needed is below .
<snip>
Any other info regarding this difficulty gladly provided for the asking . Hth , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | babydr@baby-dragons.com | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+
______________________________________________________________________________ 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
______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
Hello! I see this in your eventlog make: /usr/bin/ginstall -c -m 644 'eventlog.pc' '/usr/lib/pkgconfig/eventlog.pc' Try running this prior to trying to configure/compile syslog-ng: PKG_CONFIG_PATH=/usr/lib/pkgconfig:$PKG_CONFIG_PATH Hope that helps. -- Lance Laursen Demonware Systems Engineer
On Sun, 2010-01-17 at 17:29 -0900, Mr. James W. Laferriere wrote:
Hello All , when doing a 'make install' in eventlog-0.2.10 the file eventlog.pc is NOT installed to /usr/lib64 (see .configure below) . Thus when doing a ./configure in syslog-ng-3.0.5 the configure is unable to find the file on my x86_64 based system . Hopefully everything needed is below .
The pc file is not arch specific and should be installed in ${prefix}/pkg-config And syslog-ng would be looking for this file in directories specified by PKG_CONFIG_PATH, although pkg-config has some hard-wired locations for this variable. -- Bazsi
participants (5)
-
Balazs Scheidler
-
Jakub Jankowski
-
Lance Laursen
-
Mr. James W. Laferriere
-
Pal Tamas