Dear James/Dear All

Thanks a lot for the reply.

    i made the change at line 4453 from
MYSQL_LIBS="$($MYSQL_CONFIG --libs)"
to
MYSQL_LIBS="$($MYSQL_CONFIG --libs | sed 's/\x27//g')"

to the configure file and configured, it showed these lines as
........
......
checking for openssl/ssl.h... (cached) yes
checking for openssl/err.h... (cached) yes
checking whether the OpenSSL library is multithread-enabled... yes
checking whether to compile with SSL support... yes

Configuring DB support ...
checking whether to compile with MySQL support... disabled
checking whether to compile with LibSDB support... disabled
checking whether to compile with SQLite support... disabled
checking whether to compile with Oracle support... disabled
checking whether to compile with PostgresSQL support... disabled
........
.....


but didn't get any better, the problem is same and the error is same,
may be, it is unable to compile the MySQL, and it is disabled

if the solution is that MySQL is Disabled, request to let me know how to enable it.
Thanks in advance.


error after changing the line is: 
2004-11-08 18:31:56 [5882] [0] INFO: Debug_lvl = -1, log_file = <none>, log_lvl = 0
2004-11-08 18:31:56 [5882] [0] ERROR: Group 'dlr-mysql' may not contain field 'field-url'.
2004-11-08 18:31:56 [5882] [0] ERROR: Error found on line 109 of file `gw/testkannel.conf'.
2004-11-08 18:31:56 [5882] [0] PANIC: Couldn't read configuration from `gw/testkannel.conf'.
2004-11-08 18:31:56 [5882] [0] PANIC: ./gw/bearerbox(gw_panic+0x175) [0x80c8501]
2004-11-08 18:31:56 [5882] [0] PANIC: ./gw/bearerbox(main+0x171) [0x805254d]
2004-11-08 18:31:56 [5882] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0xf8) [0xb722e748]
2004-11-08 18:31:57 [5882] [0] PANIC: ./gw/bearerbox(SSL_write+0x51) [0x80515d9]


error before changing the line was:
2004-11-08 16:59:20 [4147] [0] INFO: Debug_lvl = -1, log_file = <none>, log_lvl = 0
2004-11-08 16:59:20 [4147] [0] ERROR: Group 'dlr-mysql' may not contain field 'field-url'.
2004-11-08 16:59:20 [4147] [0] ERROR: Error found on line 109 of file `gw/testkannel.conf'.
2004-11-08 16:59:20 [4147] [0] PANIC: Couldn't read configuration from `gw/testkannel.conf'.
2004-11-08 16:59:20 [4147] [0] PANIC: ./gw/bearerbox(gw_panic+0x175) [0x80c8501]
2004-11-08 16:59:20 [4147] [0] PANIC: ./gw/bearerbox(main+0x171) [0x805254d]
2004-11-08 16:59:20 [4147] [0] PANIC: /lib/tls/libc.so.6(__libc_start_main+0xf8) [0xb722e748]


On Mon, 2004-11-08 at 17:38, James Coleman wrote:
On Mon, Nov 08, 2004 at 04:07:13PM +0530, shyam kumar wrote:
> 
>    Dear James/Dear all
>        did u got your problem resolved of the dlr connectivity to the
>    mysql database, i am also facing the same problem and hope to get the
>    answer from U, if your problem gets solved, by the way i am using the
>    kannel 1.3.2 version and mysql 4.0.20. and the error i am getting is
>    

Yes, the problem is solved

Alejandro found the problem and solution, it's in the list archives somewhere.

The call to mysql_config from configure script doesn't handle quoted cflags
 param okay.

I found it.


 So, what I did was to modify the configure script on line 4453:
 
  Before:
        MYSQL_LIBS="$($MYSQL_CONFIG --libs)"
 
  After:
        MYSQL_LIBS="$($MYSQL_CONFIG --libs | sed 's/\x27//g')"


Try that. I can't remember was there a patch :-7

Not exactly sure what kannel version that solution was for so the 
line you find  MYSQL_LIBS="$($MYSQL_CONFIG --libs)"  at in the
configure file might be different?  

Hopefully that'll work okay for you.

James.
 
--
shyam kumar <[EMAIL PROTECTED]>
Tanla Solutions Ltd



*****************************************************************************

This e-mail and any files transmitted with it are for the sole use
of the intended recipient(s) and may contain confidential and privileged
information. If you are not the intended recipient, please contact the 
sender by reply e-mail and destroy all copies of the original message.
 
Any unauthorized review, use, disclosure, dissemination, forwarding, 
printing or copying of this email or any action taken in reliance on 
this e-mail is strictly prohibited and may be unlawful.

*****************************************************************************

Reply via email to