Re: configure on FreeBSD

Just try compiling and see what happens :)

You probably dont want to be using ODBC, the postgresql tests look ok -
back in the day there was a specific "Postgres with some extra informix
compatibility patches" it searched for (around version 7.4), perhaps
slightly interestingly to you - that work was done for Loblaws back in the
day.
The only thing might be "mysql" stuff - do you want to use Mysql ?
Postgresql ? Informix ? for your database ?

On Thu, 7 Jan 2021 at 16:01, James B. Byrne via Aubit4gl-discuss <
[email protected]> wrote:

> I am working on resolving or explaining any anomalies in the configure
> script.
> I am passing these options to configure:
>
> /configure --prefix=$HOME/usr/local \
>             --exec-prefix=$HOME/usr/local \
>             --sysconfdir=/usr/local/etc \
>             --with-build-cc=/usr/local/bin/gcc \
>             --with-build-cflags="-lm" \
>             --with-build-cppflags="-I/usr/include -I/usr/local/include" \
>             --with-build-ldflags="-L/usr/lib -L/usr/local/lib" \
>             --with-build-libs="/lib /usr/lib /usr/local/lib" \
>             --with-iodbc=/usr/local/lib \
>             --with-java=/usr/local/openjdk11 \
>             --with-pgsqleng=/var/db/postgres/data11
>
>
> The anomalies are:
>
> . . .
> checking for default SQLite odbc.ini entry... /etc/odbc.ini or ~/.odbc.ini
> not
> found or not writable
>
> On FreeBSD odbc.ini is found in /usr/local/etc/.  How do I tell configure
> to
> find it?
>
> . . .
> Checking for MySQL client library support:
> expr: illegal option -- L
> expr: usage: expr [-e] expression
>
> checking for mysql_stmt_close in -lmysqlclient... no
> checking for mysql_stmt_close in -lmysqld... no
> Missing MySQL client library file
> checking MySQL client support... no
> checking MySQL embedded support... no
>
>
> MySQL-client is installed.  FreeBSD does not use bash as the default sh.
> I can
> change configure to use #!/usr/bin/env bash instead but within the script
> itself it refers to bash explicitly.  In any case, the illegal option
> error is
> still raised suggesting that it is contained in a subscript.  How is a
> solution
> to this generalized?
>
> . . .
> Checking for PostgresSQL ESQL pre-compiler:
> checking for ecpg... /usr/local/bin/ecpg
> checking PG ESQL Informix compatibility... No-Invalid version number
> format-12.4
> checking PG ESQL Informix compatibility... No-'informix' identifier not
> found-12.4 ecpg
> not allowed
>
> I have no idea what this means or how to fix it.  PostgreSQL-client-12 is
> installed on the build system.
>
> . . .
> Checking for PostgreSQL ODBC driver support:
> LDFLAGS=-L/usr/lib
> CPPFLAGS=-I/usr/include
> checking for main in -lodbcpsql... no
> checking for main in -lpsqlodbc... no
> checking PG ODBC connector support... No -missing library
>
> On FreeBSD these are called:
> -rwxr-xr-x  1 root  wheel  513192 Dec 12 23:09 /usr/local/lib/psqlodbca.so
> -rwxr-xr-x  1 root  wheel  541864 Dec 12 23:09 /usr/local/lib/psqlodbcw.so
>
> How do I handle this in a generalized way so that the configure script is
> not
> broken?  I presume that an addition to configure.in to test for FreeBSD is
> required.  But I am not up to that task myself.  At least not yet.
>
>
> And, I think that this message may contain a misspelling:
>
> checking Aubit programs optimisation... No. -> Debuggig <- is enabled - set
> DEBUG=ALL to get debug.out trace.
>
>
>
>
> _______________________________________________
> Aubit4gl-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/aubit4gl-discuss
>

_______________________________________________
Aubit4gl-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/aubit4gl-discuss