Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2FFobx21306 for ; Thu, 15 Mar 2001 10:50:37 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f2FFoCt13835; Thu, 15 Mar 2001 10:50:13 -0500 (EST) To: "J. T. Vermeulen" cc: =?iso-8859-1?Q?St=E9phane?= EVEILLARD , pgsql-interfaces@postgresql.org Subject: Re: Big trouble with libpq++ In-reply-to: <20010315133432.E6118@cistron.nl> References: <007b01c0ad1b$1be5ef70$1001000a@arianeii.com> <20010315130713.C6118@cistron.nl> <008e01c0ad4c$c05aa6a0$1001000a@arianeii.com> <20010315133432.E6118@cistron.nl> Comments: In-reply-to "J. T. Vermeulen" message dated "Thu, 15 Mar 2001 13:34:32 +0100" Date: Thu, 15 Mar 2001 10:50:12 -0500 Message-ID: <13832.984671412@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/135 X-Sequence-Number: 1296 "J. T. Vermeulen" writes: > You should be able to solve this either by linking dynamically, or if you > want to stick with the static version, to link with libpq as well as libpq++. Yes, for a static link you should say -lpq++ -lpq not only -lpq++. Actually, I'd tend to do that for a dynamic link too... can't hurt. regards, tom lane