Your message dated Fri, 11 Feb 2005 20:17:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#293880: fixed in clearsilver 0.9.13-3
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; 6 Feb 2005 15:38:47 +0000
>From [EMAIL PROTECTED] Sun Feb 06 07:38:47 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp.telefonica.net (telesmtp4.mail.isp) [213.4.129.135]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CxoUo-0003Ek-00; Sun, 06 Feb 2005 07:38:46 -0800
Received: from [192.168.1.110] ([217.172.66.230]) by
telesmtp4.mail.isp (terra.es) with ESMTP id IBHY4I00.3AS for
<[EMAIL PROTECTED]>; Sun, 6 Feb 2005 16:38:42 +0100
Subject: FTBFS: Should disable mono bindings.
From: Emilio =?ISO-8859-1?Q?Jes=FAs?= Gallego Arias <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Sun, 06 Feb 2005 16:39:10 +0100
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.3
Content-Transfer-Encoding: 7bit
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:
Subject: FTBFS: Should disable mono bindings.
Package: clearsilver
Severity: serious
Justification: no longer builds from source
tags +patch
Hi!
I tried to build clearsilver on my host, and got a FTBFS:
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -fPIC -I../ -I/usr/include/python2.3 -c neo_cgi.c -o
build/temp.linux-i686-2.3/neo_cgi.o
gcc -pthread -shared build/temp.linux-i686-2.3/neo_cgi.o
build/temp.linux-i686-2.3/neo_cs.o build/temp.linux-i686-2.3/neo_util.o
-L../libs -lz -lneo_cgi -lneo_cs -lneo_utl -o neo_cgi.so
make[2]: Leaving directory
`/home/emilio/fuentes/debian/clearsilver/clearsilver-0.9.13/build-tree/clearsilver-0.9.13/python'
make[2]: Entering directory
`/home/emilio/fuentes/debian/clearsilver/clearsilver-0.9.13/build-tree/clearsilver-0.9.13/dso'
/usr/bin/ld -rpath ../libs -shared -o libneo.so
-whole-archive ../libs/libneo_cgi.a ../libs/libneo_cs.a ../libs/libneo_utl.a
-no-whole-archive -lz -L../libs/
gcc -o dsotest dsotest.c -lneo -L. -I..
make[2]: Leaving directory
`/home/emilio/fuentes/debian/clearsilver/clearsilver-0.9.13/build-tree/clearsilver-0.9.13/dso'
make[2]: Entering directory
`/home/emilio/fuentes/debian/clearsilver/clearsilver-0.9.13/build-tree/clearsilver-0.9.13/csharp'
/usr/bin/mcs -target:library --unsafe CS.cs -out:clearsilver.dll
CS.cs(84) error CS0214: Pointers may only be used in an unsafe context
Compilation failed: 1 error(s), 0 warnings
make[2]: *** [clearsilver.dll] Error 1
make[2]: Leaving directory
`/home/emilio/fuentes/debian/clearsilver/clearsilver-0.9.13/build-tree/clearsilver-0.9.13/csharp'
make[1]: *** [cs] Error 2
make[1]: Leaving directory
`/home/emilio/fuentes/debian/clearsilver/clearsilver-0.9.13/build-tree/clearsilver-0.9.13'
make: *** [debian/stamp-makefile-build] Error 2
This is caused because I have mono-dev installed and configure tried to
build mono bindings, which seem broken.
The workaround is to disable mono bindings:
--- rules.old 2005-02-06 15:06:07.557676648 +0100
+++ rules 2005-02-06 14:50:12.671841360 +0100
@@ -10,6 +10,7 @@
DEB_CONFIGURE_EXTRA_FLAGS := --with-python=/usr/bin/python2.3 \
--disable-perl \
+ --disable-csharp \
--disable-ruby \
--disable-apache \
--enable-gettext
Regards and thank you for taking care of this,
Emilio
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
---------------------------------------
Received: (at 293880-close) by bugs.debian.org; 12 Feb 2005 01:23:11 +0000
>From [EMAIL PROTECTED] Fri Feb 11 17:23:11 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Czm07-0002cN-00; Fri, 11 Feb 2005 17:23:11 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CzluL-0003Mz-00; Fri, 11 Feb 2005 20:17:13 -0500
From: Otavio Salvador <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#293880: fixed in clearsilver 0.9.13-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 11 Feb 2005 20:17:13 -0500
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 2
Source: clearsilver
Source-Version: 0.9.13-3
We believe that the bug you reported is fixed in the latest version of
clearsilver, which is due to be installed in the Debian FTP archive:
clearsilver-dev_0.9.13-3_i386.deb
to pool/main/c/clearsilver/clearsilver-dev_0.9.13-3_i386.deb
clearsilver_0.9.13-3.diff.gz
to pool/main/c/clearsilver/clearsilver_0.9.13-3.diff.gz
clearsilver_0.9.13-3.dsc
to pool/main/c/clearsilver/clearsilver_0.9.13-3.dsc
python-clearsilver_0.9.13-3_all.deb
to pool/main/c/clearsilver/python-clearsilver_0.9.13-3_all.deb
python2.3-clearsilver_0.9.13-3_i386.deb
to pool/main/c/clearsilver/python2.3-clearsilver_0.9.13-3_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.
Otavio Salvador <[EMAIL PROTECTED]> (supplier of updated clearsilver 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, 11 Feb 2005 22:47:25 -0200
Source: clearsilver
Binary: python2.3-clearsilver clearsilver-dev python-clearsilver
Architecture: source i386 all
Version: 0.9.13-3
Distribution: unstable
Urgency: medium
Maintainer: Jesus Climent <[EMAIL PROTECTED]>
Changed-By: Otavio Salvador <[EMAIL PROTECTED]>
Description:
clearsilver-dev - headers and static library for clearsilver
python-clearsilver - python bindings for clearsilver
python2.3-clearsilver - python bindings for clearsilver
Closes: 293574 293880
Changes:
clearsilver (0.9.13-3) unstable; urgency=medium
.
[ Priority set to 'medium' since it's blocking trac to move to sarge and
this package is already included on unstable for a long time. ]
* debian/control:
- Change clearsilver-dev dependency to python-clearsilver.
Closes: #293574;
* debian/rules:
- Skip mono bindings by now. It'll come back in next releases;
Closes: 293880;
Files:
ddf939e1e145a3b37c598b4e3edc7ed9 720 devel optional clearsilver_0.9.13-3.dsc
bf328b82dd30a0a20f86d3c1c41e6d0b 3305 devel optional
clearsilver_0.9.13-3.diff.gz
9829661fe45044be1daa1a34fdaf953e 4618 python optional
python-clearsilver_0.9.13-3_all.deb
8e8109513ad75635e349558ef6294f3d 4724 python optional
clearsilver-dev_0.9.13-3_i386.deb
21f23dba11123bb6c014aa6c33a7f2e7 79664 python optional
python2.3-clearsilver_0.9.13-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCDVVULqiZQEml+FURArbYAJ4pCGApLAcOWvkTWkYFBtNCIzwc8wCfcjNs
qwusRxURdOG+UIBfL4eX1Lg=
=oPAO
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
