Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 65DDA6327B8 for ; Tue, 8 Jun 2010 08:58:50 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 39020-05 for ; Tue, 8 Jun 2010 11:58:37 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mail.postgresql.org (Postfix) with ESMTP id BCCC8632520 for ; Tue, 8 Jun 2010 08:58:38 -0300 (ADT) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta02.westchester.pa.mail.comcast.net with comcast id TPPp1e0020bG4ec52PyeNg; Tue, 08 Jun 2010 11:58:38 +0000 Received: from sz0093.wc.mail.comcast.net ([76.96.58.151]) by omta03.westchester.pa.mail.comcast.net with comcast id TPye1e0043FmDic3PPyed9; Tue, 08 Jun 2010 11:58:38 +0000 Date: Tue, 8 Jun 2010 11:58:37 +0000 (UTC) From: Lou Picciano To: pgsql-testers Message-ID: <1189685051.3112741275998317894.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> In-Reply-To: <1667384213.3112031275998189299.JavaMail.root@sz0093a.westchester.pa.mail.comcast.net> Subject: v9 beta 2 - Build on Solaris SPARC - links to two different libxml2 implementations? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_161877_2059646492.1275998317893" X-Originating-IP: [76.117.184.231] X-Mailer: Zimbra 5.0.19_GA_3172.RHEL5_64 (ZimbraWebClient - SAF3 (Mac)/5.0.19_GA_3177.RHEL5_64) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.791 tagged_above=-10 required=5 tests=BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201006/4 X-Sequence-Number: 118 ------=_Part_161877_2059646492.1275998317893 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit [TEST REPORT] [Release]: 9.0beta2 - via source [Test Type]: Configure and Install [Test]: Build of PostgreSQL on Solaris; as usual, it's a nice, smooth, easy process. Thanks, Team! We tend to build with custom packages, sometimes custom-built themselves, so experiment with the various environment variables to see if they get us where we want to be: export LDFLAGS="-L/usr/local/lib -R/usr/local/lib -L/usr/local/ssl/lib -R/usr/local/ssl/lib" export LIBS=" -lssl -lcrypto -lsasl2 -lz -lm" export CPPFLAGS="-I/usr/local/include -I/usr/local/ssl/include" export PYTHON="/usr/local/bin/python3" [Platform]: Solaris quad Enterprise 450 [Parameters]: We do have libxml2 installed, under the /usr/local 'tree' and, for the moment, have made no effort to remove any SUN-provided xml2 package. [Failure]: NO [Results]: Configure/Build proceeds smoothly, without error. But linking appears to be looking for two different versions of libxml...?? Checking results of linking produces the following - ambiguous? - output: # ldd src/backend/postgres ... libxml2.so.2 => /usr/local/lib/libxml2.so.2 ... libxml2.so.2 (SUNW_1.6) => (version not found) [Comments]: Haven't yet assessed what the impact of this might be at runtime; wanted to run it by the experts first. ------=_Part_161877_2059646492.1275998317893 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <= div style=3D'font-family: Verdana; font-size: 12pt; color: #000000'>

[TEST REPORT]

[R= elease]: 9.0beta2 - via source

[Test Type]: Configure and Install

[Test]: Build of PostgreSQL on Solaris; a= s usual, it's a nice, smooth, easy process.  Thanks, Team!

We tend to build with custom packages, sometim= es custom-built themselves, so experiment with the various environment vari= ables to see if they get us where we want to be:

export LDFLAGS=3D"-L/usr/local/lib -R/usr/lo= cal/lib -L/usr/local/ssl/lib -R/usr/local/ssl/lib"

expo= rt LIBS=3D" -lssl -lcrypto -lsasl2 -lz -lm"

export CPPF= LAGS=3D"-I/usr/local/include -I/usr/local/ssl/include"

= export PYTHON=3D"/usr/local/bin/python3"

[Platform]: Solaris quad Enterprise 450

[Parameters]: We do have libxml2 i= nstalled, under the /usr/local 'tree' and, for the moment, have made no eff= ort to remove any SUN-provided xml2 package.

[Failure]: NO

[Results]: 

Configure/= Build proceeds smoothly, without error.

But linking appears to be looking for two different versions of libxml= ...??


Checking results of linking produces the following - ambigu= ous? - output:

# l= dd src/backend/postgres  

...

=         libxml2.so.2 =3D>  /usr/local/lib/= libxml2.so.2

...

    = ;    libxml2.so.2 (SUNW_1.6) =3D>       (versio= n not found)


= [Comments]: Haven't yet assessed what the impact of this might be = at runtime; wanted to run it by the experts first.

<= /html> ------=_Part_161877_2059646492.1275998317893--