From: "eescar@free.fr" <eescar@free.fr>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH] ulogd 1.24 mysql bad identification
Date: Mon, 23 Jul 2007 01:43:15 +0200 [thread overview]
Message-ID: <46A3EB93.6080701@free.fr> (raw)
Hi list,
trying to build ulogd-1.24, ./configure give me a warning, leading to a bad identification in the mysql :
....
checking for MySQL files... found mysql_config in /usr/bin
checking for mysql_real_escape_string support... strings: invalid option -- L
Usage: strings [option(s)] [file(s)]
Display printable strings in [file(s)] (stdin by default)
The options are:
-a - --all Scan the entire file, not just the data section
-f --print-file-name Print the name of the file before each string
-n --bytes=[number] Locate & print any NUL-terminated sequence of at
-<number> least [number] characters (default 4).
-t --radix={o,d,x} Print the location of the string in base 8, 10 or 16
-o An alias for --radix=o
-T --target=<BFDNAME> Specify the binary file format
-e --encoding={s,S,b,l,B,L} Select character size and endianness:
s = 7-bit, S = 8-bit, {b,l} = 16-bit, {B,L} = 32-bit
-h --help Display this information
-v --version Print the program's version number
strings: supported targets: elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little elf32-big srec symbolsrec tekhex binary ihex trad-core
found old MySQL
.....
after some digging in the lists archives, it looks like ulogd 1.x support looks nearly "abandoned" ...
As I, and certainly some more people are, am "stucked" with kernel 2.4.x, working on a live-cd firewall distro(devil-linux), I tried to fix the
problem by myself; As I'm not developper and a "bad bash scripting guy", the patch may not be optimal but it solves the issue, at least for me :
....
checking for MySQL files... found mysql_config in /usr/bin
checking for mysql_real_escape_string support... found new MySQL
creating ./config.status
....
So, as it may help some folks around, I send it on this mailling-list ...
--- ulogd-1.24/configure.old 2007-07-22 17:24:37.000000000 -0500
+++ ulogd-1.24/configure 2007-07-22 17:18:17.000000000 -0500
@@ -1728,7 +1728,7 @@
EOF
MYSQLINCLUDES=`$d/mysql_config --include`
- MYSQLLIBS=`$d/mysql_config --libs`
+ MYSQLLIBS=`$d/mysql_config --libs | awk '{ print $1 }' | cut -c3-`
DATABASE_DIR="${DATABASE_DIR} mysql"
Thank you all for the fantastic job done,
Best Regards,
MaNU ESCaR
next reply other threads:[~2007-07-22 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 23:43 eescar [this message]
2007-07-23 8:01 ` [PATCH] ulogd 1.24 mysql bad identification Jan Engelhardt
2007-07-23 11:12 ` eescar
2007-07-23 15:10 ` Jan Engelhardt
2007-07-26 13:19 ` Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2007-07-22 22:57 MaNU ESCaR
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A3EB93.6080701@free.fr \
--to=eescar@free.fr \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.