Subject: Re: pkg/30031: Cannot compile package subversion 1.1.4 on NetBSD
To: Eric Gillespie <firstname.lastname@example.org>
From: Johnny Lam <jlam@NetBSD.org>
Date: 04/25/2005 10:20:44
Eric Gillespie wrote:
> email@example.com writes:
>>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
-- Johnny Lam <jlam@NetBSD.org>