Patrick Welche <prlw1%cam.ac.uk@localhost> writes: > On Tue, Jan 25, 2011 at 07:05:42PM +0100, Joerg Sonnenberger wrote: >> On Tue, Jan 25, 2011 at 11:59:00AM -0500, Greg Troxel wrote: >> > That often works fine; the problem is that the patches to make >> > PostgreSQL use libtool don't work right; PostgreSQL has its own fairly >> > complicated shlib spport system and in this case that seems to work >> > better than our force-libtool approach. I don't think people are >> > arguing that pkgsrc swapping in libtool is in general bad, but rather >> > that in this particular case we're worse off. >> >> Are we? How often did we have problems with the libtool build? >> Compare the history of the Darwin rules in PostgreSQL itself. It was >> broken a number of times, too. The most likely candidate for the current >> OSX fallout is -bundle. The easiest way to fix this is figure out how >> the plsql module is built in both cases (with and w/o libtool). > > I just found a round tuit to borrow someone's MacOS 10.4/XCode 2.5 laptop, > boostrapped a current pkgsrc on it, and built postgresql90 successfully, > presumably with libtool. > > I take it I missed the boat? Not sure what you mean, but the tricky part is postgis, which uses postgresql's shlib functionality. I don't remember the details, but I had a bunch of trouble - basically our libtoolification was incomplete and didn't work right for postgresql module builds.
Attachment:
pgpnBrqHqLsia.pgp
Description: PGP signature