So far, we still have not seen XView actually *working* on amd64, why I
*suggest* the same treatment for amd64 as with ia64:

diff -Naur jove-4.16.0.65/debian/control jove-4.16.0.65.fixed/debian/control
--- jove-4.16.0.65/debian/control       2005-03-22 13:33:48.756683017 +0100
+++ jove-4.16.0.65.fixed/debian/control 2005-03-22 13:32:03.688444295 +0100
@@ -1,6 +1,6 @@
 Source: jove
 Section: editors
-Build-Depends: debhelper (>= 4.1.16), libncurses-dev, xlibs-dev, xviewg-dev 
[!ia64], groff
+Build-Depends: debhelper (>= 4.1.16), libncurses-dev, xlibs-dev, xviewg-dev 
[!ia64 !amd64], groff
 Priority: optional
 Maintainer: Cord Beermann <[EMAIL PROTECTED]>
 Standards-Version: 3.6.1.0
diff -Naur jove-4.16.0.65/debian/rules jove-4.16.0.65.fixed/debian/rules
--- jove-4.16.0.65/debian/rules 2005-03-22 13:33:48.757682839 +0100
+++ jove-4.16.0.65.fixed/debian/rules   2005-03-22 13:31:32.261055971 +0100
@@ -19,9 +19,11 @@
 
 build-xjove:
 ifneq ($(DEB_HOST_ARCH), ia64)
+ifneq ($(DEB_HOST_ARCH), amd64)
        dh_testdir
        $(MAKE) makexjove
 endif
+endif
 
 binary: binary-arch binary-indep
 
@@ -29,6 +31,9 @@
 ifeq ($(DEB_HOST_ARCH), ia64)
        export DH_OPTIONS=-pjove
 endif
+ifeq ($(DEB_HOST_ARCH), amd64)
+       export DH_OPTIONS=-pjove
+endif
        dh_testdir
        dh_testroot
        dh_installdebconf
@@ -48,10 +53,12 @@
        dh_builddeb -pjove
 # dh_gencontrol or something seem to not honour DH_OPTIONS
 ifneq ($(DEB_HOST_ARCH), ia64)
+ifneq ($(DEB_HOST_ARCH), amd64)
        dh_gencontrol -pxjove
        dh_md5sums -pxjove
        dh_builddeb -pxjove
 endif
+endif
 
 binary-indep: build install
 # does nothing.
@@ -67,12 +74,14 @@
 
 install-xjove: build-xjove
 ifneq ($(DEB_HOST_ARCH), ia64)
+ifneq ($(DEB_HOST_ARCH), amd64)
        export DH_OPTIONS=-pxjove
        dh_testdir
        dh_testroot
        dh_installdirs
        $(MAKE) installxjove DESTDIR=`pwd`/debian/xjove
 endif
+endif
 
 clean:
        dh_testdir

-ukh


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to