On Sun, Mar 06, 2005 at 03:59:04PM +0100, Santiago Vila <[EMAIL PROTECTED]> wrote: > While building this package for the hurd-i386 architecture, I noticed > that there is a hardcoded dependency on libc0.2, which does not exist. > > Then I noticed about the debian/mkdep script, which seems like a hack.
Indeed it is. > It was my understanding that statically linked executables, by definition, > do not depend on libc at all, so the package dependency is artificial, > but if I'm missing anything and there is a real need to depend on the > libc of the day, then please do it in a portable way, which does not > need to be updated for every architecture. For example, you could > include a simple "hello world" program in the package source and just > compile and run dpkg-shlibdeps on it. You're probably absolutely right about the libc6 dependency not being there, now that I think it through. I suspect it is probably there out of sheer force of habit, where compiled binaries are concerned. Unless anyone raises objections, I'll remove the dependency. -- Mike Markley <[EMAIL PROTECTED]> I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones. - Albert Einstein. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
