In article <[EMAIL PROTECTED]> (gmane.linux.debian.devel.x) you wrote: > Hi, I need some help or suggestions or something. My package WMRack > builds fine here--but I haven't yet upgraded to the new "modular" X. > It fails to build on Debian's autobuilders though, and I'm darned if I > have any idea why. I am the sole upstream maintainer of this package > as well as the Debian maintainer. Nothing has changed in the package > that should affect this.
> 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 [...] Hello, AC_PATH_X searches[1] for [Xt],[X11/Intrinsic.h],[XtMalloc (0)] by default, so this shouldn't have worked[2], as you do not build-depend on libxt-dev. Try purging libxt-dev and rebuild after dpkg-source -x. At least previously (pre-modular) there were three ways to fix this kind of bug, I guess all of them should continue to work. 1) --x-includes=/usr/include --x-libraries=/usr/lib 2) (uselessly) build-depend on libxt-dev 3) invoke AC_PATH_X with arguments to search for a library/header/function you need anyway, instead of the default [Xt],[X11/Intrinsic.h],[XtMalloc (0)], e.g.: -AC_PATH_X +AC_PATH_X([X11],[Xlib.h],[XInitExtension()]) 1 will break backports to non-modular, 3 is the cleanest (--> upstream) but will bloat the diff due to the need to regenerate the complete auto-foo, so I would go for 2 in the Debian package. cu andreas [1] unless this has changed in modular, but I do not think so. [2] according to the build-logs it has, though. ;-) -- 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]
