Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 18E30632F2C for ; Wed, 30 Dec 2009 12:35:07 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 63422-02 for ; Wed, 30 Dec 2009 16:34:56 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.postgresql.org (Postfix) with ESMTP id 2B5F9632F3C for ; Wed, 30 Dec 2009 12:34:56 -0400 (AST) Received: from [192.168.1.3] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0LzYZu-1O33Z41zne-014Btu; Wed, 30 Dec 2009 17:34:41 +0100 Message-ID: <4B3B8109.6070604@2ndquadrant.com> Date: Wed, 30 Dec 2009 11:34:17 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: postgresql@raveland.org CC: pgsql-testers@postgresql.org Subject: Re: [Postgresql alpha3] Configure fails with --libxml on OpenBSD References: <20091230110717.GB15571@coredump.raveland.priv> In-Reply-To: <20091230110717.GB15571@coredump.raveland.priv> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19KGx01g3IGeHjiD1YtCBjDQUby9hE1ER/eI7a 7THWu6k5drxiskmfss5G2KaQc9rARqKN3hHCb0MwEKdBRUQ+BF haRQzI+UCQmxrTtBYBc/l3LAVvqNZ2T X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.51 tagged_above=-10 required=5 tests=AWL=0.089, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200912/4 X-Sequence-Number: 16 postgresql@raveland.org wrote: > I don't understand why the detection of both -pthread and -lpthread fails with --libxml (may > the messages about strcpy/strcat be the cause) ? > Those warning are just that: warnings, nothing related to your problem. My first guess is that you're using a libxml from before thread safety was introduced, or have a version that wasn't compiled to support it: http://xmlsoft.org/threads.html There was a recent change to PostgreSQL that switched the default to turning on thread safety for clients when you build. You can easily turn it back off again with passing --disable-thread-safety if you just don't have an installed libxml that is thread-safe. -- Greg Smith 2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.com