On 2006-04-29 Andreas Metzler <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]> (gmane.linux.debian.devel.x) you wrote: [cannot find X] > > The build-dependencies (which worked before) are: "libx11-dev, > > libxext-dev, libxpm-dev, xutils, debhelper (>= 4.0.0)" and the > > autoconf stanza (from configure.in) is, simply:
> > dnl check for X11 > > dnl > > AC_PATH_X > [...] > AC_PATH_X searches[1] for [Xt],[X11/Intrinsic.h],[XtMalloc (0)] by > default, so this shouldn't have worked[2], I know now why it has worked previously: You are build-depending on xutils, which used to contain xmkmf. - The autoconf test uses xmkmf if available and only checks for libXt if xmkmf is not available. In modular xmkmf lives in xutils-dev. So I guess you should simply build depend on libxt-dev instead of xutils. This way your package will be buildable on sarge and sid. [...] > [1] unless this has changed in modular, but I do not think so. Hello, Obviously this has nothing to do with modular, as the test is not part of X but of autoconf. Debian's autoconf 2.59a-4 contains a changed test that searches for X11/Xlib.h and XrmInitialize (See bug #327655), but this will only make a change to *your* package if you rebuild configure from configure.ac (or .in) using the new autoconf package. This would bloat the diff and require some touch magic in debian/rules. cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken. (c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
