Comments on: Subversion and undefined symbols

By: Ryan Schmidt

Ryan Schmidt — Sun, 01 Feb 2009 21:08:52 +0000

A ticket has been filed with MacPorts now:

http://trac.macports.org/ticket/18301

By: farkinga

farkinga — Sun, 01 Feb 2009 02:30:43 +0000

Great! This is exactly what I was looking for. I am using Intel OS X 10.4

Macports indirectly relies on the raw tarball (I believe) so this might not be such a rare case, after all… I tried filing a bug about this with macports, but alas their copy of trac doesn’t appear to be functioning at the moment. There’s a related post at http://www.nabble.com/libtool-shipped-with-subversion-1.5.5-is-b0rk3d-on-Macports.-td21443432.html

I install macports stuff into /opt/local, so I copied /opt/local/bin/glibtool instead of /usr/bin/glibtool, but with that minor change, everything worked for me.

Thanks!

By: yiming

yiming — Tue, 20 Jan 2009 01:39:12 +0000

Thanks for submitting this. It’s a fairly obscure edge case, so I figure no one will care but the few people who run into it, and so I didn’t bother doing any further debugging. I’d guess very few people even try to compile SVN on OS X from raw tarball these days. But if it does turn out to be something worth investigating, then it’s definitely good for it be out there beyond my compilation notes.

By: aphor

aphor — Tue, 13 Jan 2009 19:54:00 +0000

Thanks!

I passed this on to the nice folks:
http://subversion.tigris.org/bugs.html

Let’s check the bug database from time to time and see if they care?

http://subversion.tigris.org/issue-tracker.html