Eric Gillespie wrote:
> woeye@mac.com writes:
> 
> 
>>/bin/rm /usr/pkg/lib/python2.3/site-packages/libsvn/*.a
>>rm: /usr/pkg/lib/python2.3/site-packages/libsvn/*.a: No such file or directory
>>*** Error code 1
> 
> 
> I can't reproduce this problem on 2.0.2/i386.  Does the
> workaround i committed work for you?  It should...
> 
> Actually, those rm commands are themselves a workaround.  I never
> understood why libtool was building .a files for a Python
> extension; it seems like a bug, and the submitter's system is
> actually doing the right thing.

Can that package be taught to use shlibtool instead of libtool? 
shlibtool will only build the .la file and the shared library/module, as 
opposed to libtool which will also build the .a file.  Then the "rm" 
hack won't be needed.  Note, however, that shlibtool is purely a pkgsrc 
beast.

	Cheers,

	-- Johnny Lam <jlam@NetBSD.org>