Opened 20 years ago

Closed 20 years ago

Last modified 19 years ago

#1772 closed defect (fixed)

subversion-1.0.2 fails to link tests; port build fails

Reported by: lars@… Owned by: danielluke (Daniel J. Luke)
Priority: Normal Milestone:
Component: ports Version: 1.0
Keywords: Cc:
Port:

Description

subversion-1.0.2 fails to build:

# sudo port build subversion ... cd subversion/tests/libsvn_subr && /bin/sh /usr/local/src/darwinports/dports/devel/subversion/ work/subversion-1.0.2/libtool --silent --mode=link gcc -g -O2 -g -O2 -DNEON_ZLIB -DNEON_SSL -L/opt/local/lib -rpath /opt/local/lib -o utf-test utf-test.o ../../../subversion/tests/libsvn_test-1.la ../ ../../subversion/libsvn_subr/libsvn_subr-1.la /opt/local/lib/libaprutil-0.la -ldb-4 -lexpat -liconv /opt/ local/lib/libapr-0.la -lresolv ld: Undefined symbols: _svn_utfcstring_is_valid _svn_utfis_valid _svn_utflast_valid _svn_utflast_valid2

Change History (5)

comment:1 Changed 20 years ago by danielluke (Daniel J. Luke)

Owner: changed from darwinports-bugs@… to dluke@…

assigning to myself as I'm the maintainer.

comment:2 Changed 20 years ago by danielluke (Daniel J. Luke)

Status: newassigned

Can you run:

sudo port uninstall subversion sudo port clean subversion sudo port -d -v install subversion

... and then either send me the complete output, or attach it to the bug here so I can see where this might be going wrong?

Could you also let me know what platform you're using and which version of gcc you have selected?

(uninstalling an installed subversion and then attempting to install it might fix things since the subversion build system is a little finicky about installed libraries with the same name as the ones it is building).

I haven't been able to replicate this problem on my machines.

Thanks!

comment:3 Changed 20 years ago by danielluke (Daniel J. Luke)

Can you run:

sudo port uninstall subversion sudo port clean subversion sudo port -d -v install subversion

... and then either send me the complete output, or attach it to the bug here so I can see where this might be going wrong?

Could you also let me know what platform you're using and which version of gcc you have selected?

(uninstalling an installed subversion and then attempting to install it might fix things since the subversion build system is a little finicky about installed libraries with the same name as the ones it is building).

I haven't been able to replicate this problem on my machines.

Thanks!

comment:4 Changed 20 years ago by mww@…

works here for me on 10.3.3 (tested it before commiting, too)

comment:5 Changed 20 years ago by lars@…

Resolution: fixed
Status: assignedclosed

Thank you.

I had a subversion-0.3.7 previously installed, but your suggestion:

sudo port uninstall subversion sudo port clean subversion sudo port install subversion

resolved the problem.

A pristine install would not have triggered the bug. I had tried:

sudo port clean subversion sudo port install subversion

but it wasn't enough.

The unresolved external from the original report are a recent addition, see:

http://www.contactor.se/~dast/svn/archive-2004-02/0082.shtml

So I guess you are right that an old, installed, version of a library was picked up before the newly built one.

I have marked the bug as FIXED - this sort of problem needs fixing in the subversion Makefiles if at all.

Note: See TracTickets for help on using tickets.