On Mon, 2010-05-10 at 10:59:25 +0200, Cristian Ionescu-Idbohrn wrote: > And when you're at it, I dare to have one more wish :) > > I'm cross-building libbsd for an embedded system, and I need the > symlink to _not_ point to the host installed lib, but to the > cross-built one (inside the installed directory tree). I hacked the > Makefile to do it: > > - ln -sf $(libdir)/$(LIB_SHARED) $(DESTDIR)$(usrlibdir)/$(LIB_SHARED_SO) > + ln -sf ../..$(libdir)/$(LIB_SHARED) > $(DESTDIR)$(usrlibdir)/$(LIB_SHARED_SO) > > but I'm convinced there's a better (although more intricate) way to do > it.
The problem with this patch is that it assumes the relationship between libdir and usrlibdir is fixed and there's always going to be two directories below. The question though, is why do you need this at all? I assume you are placing the files on a different path from the intended on the target? This is problematic, and you'll probably find that all other packages which have the shared library in /lib but the .so symlink in /usr/lib (as it should be) fail in your case. regards, guillem -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100515234235.gb24...@gaara.hadrons.org
