Re: [Help-gnu-radius] SQL Authentication Failure

[Kevin]

> Strange. There should at least be a line saying:
>
> configure:<lineno>: checking for -lmysqlclient
>
> Try to reconfigure the package (do not forget to remove config.cache
> beforehand) and examine the output from configure. If everything is
> OK it should say something like
>
> checking for -lmysqlclient... -lm -L/usr/local/lib/mysql -lmysqlclient

Ok, I found out why I wasn't getting anything in the config.log file.  I had
run configure with the --with-sql option as stated in the README file
instead of using --with-mysql.  When using the --with-mysql option the
configure works properly.

> Yes, possibly you have. Check where exactly are mysql libraries and
> headers located on your system. The two locations configure knows
> about are /usr/local/lib/mysql and /usr/lib/mysql. The includes
> are referred to in the sources as mysql/mysql.h, so usual include
> path should suffice in most cases. However, if mysql was installed
> under a different prefix, you will have to specify both
> --with-lib-path and --with-include-path. Another known problem with
> mysqlclient library is that it depends on -lz. This dependency is
> pulled in authomatically if libmysqlclient is a shared library,
> otherwise (if you have only libmysqlclient.a) you will have to specify
> it manually, e.g.:
>
>   LIBS=-lz ./configure --with-mysql ..

Ok.  As noted above the configure now completes correctly, but I believe I'm
still having a problem with the includes.  I am admitedly not even close to
a programming expert, and am not clear on how to go about finding what dir
to specify for --with-include.  When trying to compile I am currently
getting the error:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -g -02 -c -mysql.c  -fPIC -DPI
C -o .libs/mysql.lo
mysql.c:43:25: mysql/mysql.h: No such file or directory
make[2]: *** [mysql.lo] Error 1
make[2]: Leaving directory '/usr/local/src/gnu-radius-0.96.2/sql'

Sorry if this is a basic question, but I haven't the foggiest idea where to
go from here.

Thanks for the continued help,
Kevin