Your message dated Tue, 01 Feb 2005 11:11:56 -0500
with message-id <[EMAIL PROTECTED]>
and subject line nip2 now builds on all debian architectures
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Oct 2004 12:24:06 +0000
>From [EMAIL PROTECTED] Fri Oct 22 05:24:06 2004
Return-path: <[EMAIL PROTECTED]>
Received: from apate.telenet-ops.be [195.130.132.57]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CKySk-0006Gd-00; Fri, 22 Oct 2004 05:24:06 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
by apate.telenet-ops.be (Postfix) with SMTP id 67F342480F6
for <[EMAIL PROTECTED]>; Fri, 22 Oct 2004 14:24:02 +0200 (MEST)
Received: from kabel.telenet.be (D5775FD9.kabel.telenet.be [213.119.95.217])
by apate.telenet-ops.be (Postfix) with ESMTP id 48031248141
for <[EMAIL PROTECTED]>; Fri, 22 Oct 2004 14:24:02 +0200 (MEST)
Received: by kabel.telenet.be (Postfix, from userid 501)
id AB8C526136; Fri, 22 Oct 2004 14:24:01 +0200 (CEST)
Date: Fri, 22 Oct 2004 14:24:01 +0200
From: Kurt Roeckx <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: nip: FTBFS: initializer element is not constant
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: nip
Version: 7.8.14-1
Severity: important
It's failing to build on some arches (amd64, ia64 and hppa atleast)
with the following error:
if cc -DHAVE_CONFIG_H -I. -I. -I.. -pthread -I/usr/include/
-I/usr/include/gtk-
1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include
-I/usr/include/libxml2
-g -Wall -O2 -MT imageview.o -MD -MP -MF ".deps/imageview.Tpo"
\
-c -o imageview.o `test -f 'imageview.c' || echo
'./'`imageview.c; \
then mv -f ".deps/imageview.Tpo" ".deps/imageview.Po"; \
else rm -f ".deps/imageview.Tpo"; exit 1; \
fi
imageview.c:578: warning: initializer element is not computable
at load time
imageview.c:578: error: initializer element is not constant
imageview.c:578: error: (near initialization for `imageview_menu_items[40].call
back_action')
imageview.c:578: error: initializer element is not constant
imageview.c:578: error: (near initialization for `imageview_menu_items[40]')
imageview.c:580: warning: initializer element is not computable at load time
imageview.c:580: error: initializer element is not constant
imageview.c:580: error: (near initialization for `imageview_menu_items[41].call
back_action')
imageview.c:580: error: initializer element is not constant
imageview.c:580: error: (near initialization for `imageview_menu_items[41]')
make[4]: *** [imageview.o] Error 1
In the ia64 and amd64 build logs we also see things like this:
action.c:1154: warning: cast from pointer to integer of different size
action.c:1154: warning: cast to pointer from integer of different size
Those ussualy mean it's not 64 bit clean and might cause problems
on 64 bit architetures.
Those seems to be caused by the following part of the PEPUTP macro:
void *v99 = (void*)((int)(V));\
Why are all those casts needed?
There are lots of other warnings too, see the buildd logs.
Kurt
---------------------------------------
Received: (at 277784-done) by bugs.debian.org; 1 Feb 2005 19:30:05 +0000
>From [EMAIL PROTECTED] Tue Feb 01 11:30:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from through.apexcovantage.com (through.acv.apexcovantage.com)
[65.166.131.3]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cw3it-00034J-00; Tue, 01 Feb 2005 11:30:04 -0800
Received: from apex.acv.apexcovantage.com ([192.168.0.1])
by through.acv.apexcovantage.com
(8.12.8/8.12.8/apexcovantage-gateway-1.0) with ESMTP id j11J4B81025959
for <[EMAIL PROTECTED]>; Tue, 1 Feb 2005 14:28:42 -0500
Received: from soup (soup.acv.apexcovantage.com [192.168.0.5])
by apex.acv.apexcovantage.com (8.12.8/8.12.8/ads-apexcovantage-hub-1.3)
with ESMTP id j11GBuUQ016237;
Tue, 1 Feb 2005 11:11:56 -0500
Received: from ejb by soup with local (Exim 4.43)
id 1Cw0dA-0005X3-Il; Tue, 01 Feb 2005 11:11:56 -0500
From: Jay Berkenbilt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: nip2 now builds on all debian architectures
Message-ID: <[EMAIL PROTECTED]>
Date: Tue, 01 Feb 2005 11:11:56 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Apex-MailScanner-Information: Scanned by Apex with MailScanner
X-Apex-MailScanner: Found to be clean
X-MailScanner-From: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
After inclusion of changes equivalent to the patches from bug 288707
and some other changes applied upstream, the latest upstream release
of nip2, 7.10.8, now compiles on 64-bit architectures. This version
of nip2 is now in debian. It is not known whether nip2 is fully
functional on 64-bit systems, but the upstream maintainer has an AMD64
system coming in, so we should expect it to work very soon. In any
case, the specific FTBFS problems reported by this bug are resolved.
nip2 now exists on all architectures in debian.
Thanks again for your report.
--Jay
--
Jay Berkenbilt <[EMAIL PROTECTED]>
http://www.ql.org/q/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
