Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 53C179FB6CE for ; Fri, 16 Mar 2007 04:31:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 57298-10 for ; Fri, 16 Mar 2007 04:31:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from herakles.kfunigraz.ac.at (HERAKLES.kfunigraz.ac.at [143.50.13.36]) by postgresql.org (Postfix) with ESMTP id 3A42C9FB6C3 for ; Fri, 16 Mar 2007 04:31:12 -0300 (ADT) Received: from amphion.pers.ad.uni-graz.at ([143.50.13.21]) by herakles.kfunigraz.ac.at with Microsoft SMTPSVC(5.0.2195.6713); Fri, 16 Mar 2007 08:31:10 +0100 Received: from [143.50.238.151] ([143.50.238.151]) by amphion.pers.ad.uni-graz.at with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Mar 2007 08:31:10 +0100 Message-ID: <45FA47C0.2040601@uni-graz.at> Date: Fri, 16 Mar 2007 08:31:12 +0100 From: Dieter Schicker User-Agent: Thunderbird 1.5.0.9 (X11/20070103) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: undefined reference to `SSL_CTX_set_client_cert_cb' References: <45F8FC99.1040208@uni-graz.at> <45F9ABE2.8000807@theendofthetunnel.de> <29564.1174010740@sss.pgh.pa.us> In-Reply-To: <29564.1174010740@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Mar 2007 07:31:10.0823 (UTC) FILETIME=[11B94770:01C7679D] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/94 X-Sequence-Number: 24918 Tom Lane wrote: > Hannes Dorbath writes: >> Dieter Schicker wrote: >>> postgresql-8.2.3 on a system running debian stable with kernel 2.6.8-2-686 >>> Any ideas? > >> No, but maybe an antiquated OS and up to date applications is not the >> best match. Debian stable is somewhere around PG 7.4.x. > > But we were using SSL_CTX_set_client_cert_cb even in 7.4, and AFAICT > the function has existed in OpenSSL since 1999 or earlier. > > I did some googling and found various people complaining of similar > build problems with completely Postgres-unrelated software that's using > OpenSSL, so it seems there's something a bit odd about that particular > function ... but I didn't find out what. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster Hehe, I would never ever do that, I swear! ;-) First of all, thanks for your valuable answers! Concerning the "antiquated OS": I think this is not the right place to discuss the antiquity (right word? - sorry my mother tongue is German) of an OS. Just one sentence: I have been in the business for 25 years now and I therefore prefer stability to "always-have-to-have-the-super-freshest-software". ;-) The reason why I break this self-imposed "rule" with postgres is that we use postgres (exclusively) for teaching database courses here at our institution and we need some functionalities that require version 8.x. Tom, of course I did that googling, too before I dared to ask on this list. But all I found was questions, no answers. ;-) I will dig into that problem further and keep you informed if I find a solution. Thanks and Cheers Dieter