Received: from barbar.esat.kuleuven.ac.be (root@barbar.esat.kuleuven.ac.be [134.58.56.153]) by hub.org (8.8.8/8.8.8) with ESMTP id IAA18435 for ; Wed, 7 Oct 1998 08:57:14 -0400 (EDT) (envelope-from joris.esch@esat.kuleuven.ac.be) Received: from tintin (kn4-92.kotnet.kuleuven.ac.be [10.0.4.92]) by barbar (version 8.8.5) for with SMTP id OAA14998; Wed, 7 Oct 1998 14:57:03 +0200 (METDST) Organization: ESAT, K.U.Leuven, Belgium From: Joris Esch Reply-To: joris.esch@esat.kuleuven.ac.be To: pgsql-interfaces@postgresql.org Subject: RE: libpq++ and gcc Date: Wed, 7 Oct 1998 14:46:00 +0200 X-Mailer: KMail [version 0.7.9] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <98100714555700.00973@tintin> Content-Transfer-Encoding: 8bit Hello everybody: KaDe wrote: Did you get an answer ? I think the problem is a question of path ... you have to add something as -L.. -pq -pq++ as parameters for your gcc command. I can't remember precisely, have a look in the makefile of the libpq++ directory and try to guess. I resolved the problem of the path access copying all the headers files of postgres 1 level of directory upper. I'm sure there is a smarter way, but I've not yet found it. I hope this can help you: in /etc/profile, i have: PGLIB=/usr/lib export PGLIB My headers are in /usr/include. There i have a libpq++.h which i #include. Then, when i compile i type e.g.: c++ test_pgsql_libpq++.cpp -o test_pgsql_libpq++ -lpq++ -lpq (Lowercase L) If your headers are elsewhere, try -I/my_header_directory (Uppercase i ). I use egcs, but it doesn't differ much from gcc, i think. good luck joris -- joris esch, student in electrical engineering Power is knowledge.