Your message dated Fri, 26 Aug 2005 04:02:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#296996: fixed in scite 1.64-2
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; 26 Feb 2005 10:49:16 +0000
>From [EMAIL PROTECTED] Sat Feb 26 02:49:15 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c186089.adsl.hansenet.de (localhost.localdomain) [213.39.186.89] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1D4zVb-00042J-00; Sat, 26 Feb 2005 02:49:15 -0800
Received: from aj by localhost.localdomain with local (Exim 4.44)
        id 1D50Rf-0003bA-GG; Sat, 26 Feb 2005 12:49:21 +0100
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: scite: FTBFS (amd64/gcc-4.0): cast from 'void*' to 'guint' loses 
precision
Message-Id: <[EMAIL PROTECTED]>
Date: Sat, 26 Feb 2005 12:49:21 +0100
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: scite
Severity: normal
Tags: patch

When building 'scite' on amd64 with gcc-4.0,
I get the following error:

g++ `pkg-config --cflags gtk+-2.0` -DNDEBUG -Os -W -Wall -DGTK -DSCI_LEXER 
-DPIXMAP_PATH=\"/usr/share/pixmaps\" -DSYSCONF_PATH=\"/usr/share/scite\" -I 
../../scintilla/include -I ../src -DNO_LUA -c SciTEGTK.cxx -o SciTEGTK.o
SciTEGTK.cxx: In function 'int xsystem(const char*, const char*)':
SciTEGTK.cxx:1693: warning: missing sentinel in function call
SciTEGTK.cxx: In member function 'virtual void SciTEGTK::Execute()':
SciTEGTK.cxx:1732: warning: missing sentinel in function call
SciTEGTK.cxx: In static member function 'static void 
SciTEGTK::ButtonSignal(GtkWidget*, void*)':
SciTEGTK.cxx:2205: error: cast from 'void*' to 'guint' loses precision
make[1]: *** [SciTEGTK.o] Error 1
make[1]: Leaving directory `/scite-1.62/scite/gtk'
make: *** [build-stamp] Error 2

With the attached patch 'scite' can be compiled
on amd64 using gcc-4.0.

Regards
Andreas Jochens

diff -urN ../tmp-orig/scite-1.62/scite/gtk/SciTEGTK.cxx ./scite/gtk/SciTEGTK.cxx
--- ../tmp-orig/scite-1.62/scite/gtk/SciTEGTK.cxx       2004-10-31 
07:12:53.000000000 +0000
+++ ./scite/gtk/SciTEGTK.cxx    2005-02-23 14:33:20.000000000 +0000
@@ -2202,7 +2202,7 @@
 }
 
 void SciTEGTK::ButtonSignal(GtkWidget *, gpointer data) {
-       instance->Command((guint)data);
+       instance->Command((unsigned long)data);
 }
 
 void SciTEGTK::MenuSignal(SciTEGTK *scitew, guint action, GtkWidget *) {

---------------------------------------
Received: (at 296996-close) by bugs.debian.org; 26 Aug 2005 11:08:12 +0000
>From [EMAIL PROTECTED] Fri Aug 26 04:08:12 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1E8byI-0004jp-00; Fri, 26 Aug 2005 04:02:06 -0700
From: Michael Vogt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#296996: fixed in scite 1.64-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 26 Aug 2005 04:02:06 -0700
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-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: scite
Source-Version: 1.64-2

We believe that the bug you reported is fixed in the latest version of
scite, which is due to be installed in the Debian FTP archive:

scite_1.64-2.diff.gz
  to pool/main/s/scite/scite_1.64-2.diff.gz
scite_1.64-2.dsc
  to pool/main/s/scite/scite_1.64-2.dsc
scite_1.64-2_i386.deb
  to pool/main/s/scite/scite_1.64-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Vogt <[EMAIL PROTECTED]> (supplier of updated scite package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 26 Aug 2005 12:24:31 +0200
Source: scite
Binary: scite
Architecture: source i386
Version: 1.64-2
Distribution: unstable
Urgency: low
Maintainer: Michael Vogt <[EMAIL PROTECTED]>
Changed-By: Michael Vogt <[EMAIL PROTECTED]>
Description: 
 scite      - Lightweight GTK-based Programming Editor
Closes: 296996 320975 323634
Changes: 
 scite (1.64-2) unstable; urgency=low
 .
   * debian/patches/03_new_pango:
     - support for the new pango (closes: #320975,#323634)
   * debian/patches/04_amd65
     - make it build on amd64 (closes: #296996)
Files: 
 e70b6b3dd0e99e913359bbaff951afcf 585 editors optional scite_1.64-2.dsc
 de85b79cbc55fec83a75709502b1dca4 25025 editors optional scite_1.64-2.diff.gz
 d201bc60804392b2c3556946bb0a8ea0 650316 editors optional scite_1.64-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDDvOsliSD4VZixzQRAmRvAJwM/JUD3MK3VooSLWdoa2wIUhXPJQCgl3LV
UaVchBNszYVFyyJZt3mJLug=
=VB2q
-----END PGP SIGNATURE-----


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

Reply via email to