Prev: Easier / automatic regression-test target for ports
Next: Virtualbox consuming wcpu
From: Garrett Cooper on 7 Jul 2010 17:46
On Wed, Jul 7, 2010 at 10:02 AM, Greg Larkin <glarkin(a)freebsd.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> andrew clarke wrote:
>> On Wed 2010-07-07 02:06:39 UTC+1000, andrew clarke (mail(a)ozzmosis.com) wrote:
>>
>>> Can anyone confirm that subversion fails to build with www/neon28 and
>>> requires www/neon29?  This is not mentioned in UPDATING.
>>
>> Building subversion 1.6.11_3 with neon28-0.28.6_1 installed:
>>
>> ===>  Configuring for subversion-1.6.11_3
>> configure: Configuring Subversion 1.6.11
>> ...
>> checking for pkg-config... /usr/local/bin/pkg-config
>> configure: checking neon library
>> checking neon library version... 0.28.6
>> configure: error: cannot find Neon
>> ===>  Script "configure" failed unexpectedly.
>> Please report the problem to lev(a)freebsd.org [maintainer] and attach the
>> "/usr/ports/devel/subversion/work/subversion-1.6.11/config.log" including the
>>
>> Looking at config.log:
>>
>> configure:5698: cc -o conftest -O2 -fno-strict-aliasing -pipe  -g -O2
>> -I/usr/local/include/neon          -L/usr/local/lib
>> -L/usr/local/lib/db42 conftest.c  -L/usr/local/lib -lneon  >&5
>>
>> /usr/local/lib/libneon.so: undefined reference to `SSL_SESSION_cmp'
>>
>> At this point I thought I should try rebuilding openssl-1.0.0_2,
>> however while that's re-building I decide to grep for SSL_SESSION_cmp
>> in the neon29-0.29.3_1 sources and find this comment:
>>
>> "OpenSSL 1.0 removed SSL_SESSION_cmp for no apparent reason"
>>
>> with an apparent fix.
>>
>> So my conclusion is that building subversion needs neon29 to be
>> installed if you're using OpenSSL 1.0.  And this should probably be
>> mentioned in UPDATING...
>>
>> Thanks,
>>
>> Regards
>> Andrew
>
> Hi Andrew,
>
> I confirmed the problem here with these ports installed prior to
> upgrading to Subversion 1.6.12:
>
> openssl-1.0.0_2     SSL and crypto library
> neon28-0.28.6_1     An HTTP and WebDAV client library for Unix systems
>
> Eventually, this issue should be resolved by the following PR
> (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148295), but a full
> port build has to be performed by portmgr first.
>
> In the mean time, I think an entry in UPDATING would be helpful.  Would
> you mind writing one and assigning it to me in the PR system?  I
> resolved the problem by issuing the command:
>
> portmaster -o www/neon29 neon28
>
> and proceeding with the devel/subversion build.

Certain bits probably need to be added to detect the version
incompatibility and recommend an upgrade and/or CONFLICTS, maybe?
-Garrett
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: "Matthias Andree" on 8 Jul 2010 07:06
Garrett Cooper wrote on 2010-07-07:


> Certain bits probably need to be added to detect the version
> incompatibility and recommend an upgrade and/or CONFLICTS, maybe?

I don't have a precise idea, but some support in the ports infrastructure
would be needed to assist with the OpenSSL 1.0.0 incompatibilities
somehow. We can't patch up gazillions of ports.

--
Matthias Andree
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

First  |  Prev  | 
Pages: 1 2
Prev: Easier / automatic regression-test target for ports
Next: Virtualbox consuming wcpu