> > Anyway, I now have a sharable library, and ApplixWare is running.
> > But I don't see any candidate servers...
> > I made a ~/.odbc.ini file...
> you need one other entry which corresponds to the Postgres entry...
> You'll then see a "Postgres Database" entry in the appropriate Data
> dialog box.
OK, I followed this suggestion from the Applix folks and it helped. Here
is the file which does better:
<start .odbc.ini file>
[ODBC Data Sources]
Postgres = Postgres Data
[Postgres]
Debug = 0
CommLog = 1
Driver = /opt/postgres/current/lib/libpsqlodbc.so
<eof>
An now Applix can see some candidates. I then got an error from Applix
regarding a missing library:
/opt/applix/axdata/elfodbc: can't load library 'libodbc.so'
which was apparently in the wrong directory in the Applix distribution.
So, I made a soft link to the normal directory area, and now Applix got
further, asking me for a username and password. However, I got the
following error after that:
/opt/applix/axdata/elfodbc: can't resolve symbol 'parse_statement'
When I run "nm" on /opt/postgres/current/lib/libpsqlodbc.so.0.24 I see
the following entry:
mythos> nm libpsqlodbc.so.0.24 | grep -i parse_statement
U parse_statement
which indicates an unresolved symbol. So, I found that parse.c was not
being compiled by Makefile.unx (and my derivative) so got that compiled
and linked and things are much closer to working! :)
OK, so now I get an error message saying:
missing a username, port, or server name
if I use an entry in .odbc.ini which only specifies the driver library
(as above), and I get a similar error message when I specify an
.odbc.ini entry which looks like:
[PostgresFull]
DSN = test
Server = localhost
UID = tgl
Port = 5432
Driver = /opt/postgres/current/lib/libpsqlodbc.so
If I explicitly type the server name (as "localhost") in the Applix
dialog box, I get a different error message:
axnet: Cannot launch gateway on server
not a tcp service in /etc/services
So, anyone have any other hints? What information must be in a real
.odbc.ini file for MySQL to work? I don't have much security turned on
in Postgres, but do have the TCP/IP option specified on the server.
Tried adding an entry in /etc/services, but that alone didn't change the
error message. Anyone have more hints?? :)
- Tom
Oh, btw I have started fixing up a makefile which actually fits into the
Postgres distribution...