On Mon, Mar 14, 2005 at 03:57:21PM +0100, Tommaso Moroni wrote: > > > while on the other archs the package was built correctly. > > > What's the problem? > > > > Does your package build-depend upon xlibs-dev? > > Ehm... no! > > I still cannot understand why it could be built on the other archs.
It does seem strange, maybe I'm barking up the wrong tree. > Also, how could I find "missing" build-dep like this without wasting buildd > time? The ideal thing to do in this case would be to look at the config.log which will show you exactly why the ./configure script couldn't find X. If you have access to a host you could perform a manual build there and try it out. If not add a 'cat config.log' into the debian/rules and wait for it to be rebuilt. > I mean, I use pbuilder to find the minimum build-deps required for a package, > and > those specified for knights seemed enough because it compiled correctly. > Am I missing something? (I surely am, but I cannot see where! :) I can't either .. maybe just the configure script is doing something strange on sparc. Steve -- # The Debian Security Audit Project. http://www.debian.org/security/audit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
