Your message dated Fri, 30 Sep 2005 05:32:24 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329891: fixed in socketapi 1.7.0-1
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; 24 Sep 2005 08:54:18 +0000
>From [EMAIL PROTECTED] Sat Sep 24 01:54:18 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (tennyson.dodds.net) 
[66.93.39.86] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EJ5nW-00077t-00; Sat, 24 Sep 2005 01:54:18 -0700
Received: by tennyson.dodds.net (Postfix, from userid 1000)
        id E9151704E; Sat, 24 Sep 2005 01:54:17 -0700 (PDT)
Date: Sat, 24 Sep 2005 01:54:17 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: socketapi_1.3.2-2 (arm,hppa,m68k): FTBFS: internal compiler error: in 
cp_expr_size, at cp/cp-objcp-common.c:101
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02


--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: socketapi
Version: 1.3.2-2
Severity: serious
Justification: FTBFS

Hi Anibal,

The latest upload of socketapi has failed to build on arm and m68k, and will
also fail to build on hppa eventually, with the following error:

[...]
/bin/sh ../libtool --mode=3Dcompile g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr=
/include -g -O2 -D_REENTRANT -D_THREAD_SAFE -DSCTP_SOCKET_API -Wall -O0 -g =
-DLINUX -O0 -g -Wall -DLINUX -c -o libsctpsocket_la-internetaddress.lo =14e=
st -f 'internetaddress.cc' || echo './' nternetaddress.cc
 g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -g -O2 -D_REENTRANT -D_THR=
EAD_SAFE -DSCTP_SOCKET_API -Wall -O0 -g -DLINUX -O0 -g -Wall -DLINUX -c int=
ernetaddress.cc -MT libsctpsocket_la-internetaddress.lo -MD -MP -MF .deps/l=
ibsctpsocket_la-internetaddress.TPlo  -fPIC -DPIC -o .libs/libsctpsocket_la=
-internetaddress.o
internetaddress.cc: In member function 'String
InternetAddress::_ZTv0_n40_NK15InternetAddress16getAddressStringEj(cardinal=
) const':
internetaddress.cc:763: internal compiler error: in cp_expr_size, at cp/cp-=
objcp-common.c:101
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.0/README.Bugs>.
make[2]: *** [libsctpsocket_la-internetaddress.lo] Error 1
make[2]: Leaving directory /build/buildd/socketapi-1.3.2/socketapi'
make[1]: *** [install-recursive] Error 1
[...]

A full build log can be found at
<http://buildd.debian.org/fetch.php?&pkg=3Dsocketapi&ver=3D1.3.2-2&arch=3Da=
rm&stamp=3D1124528994&file=3Dlog&as=3Draw>.

This is a (by now) well-known bug in gcc-4.0, which unfortunately will
probably take a while to resolve.  In order to work around the bug, it is
recommended that you build-depend on g++-3.4 [arm hppa m68k] and use that
compiler explicitly on those architectures, as described by Adeodato Sim=F3
here:

   http://lists.debian.org/debian-devel-announce/2005/09/msg00000.html

Cheers,
--=20
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFDNRQ5KN6ufymYLloRArlsAKDRKEope8jvzvpgBxXhUgxJeicIkgCg0BBz
g8XremMn/4HcSJnvN4xzPcU=
=fSAA
-----END PGP SIGNATURE-----

--BOKacYhQ+x31HxR3--

---------------------------------------
Received: (at 329891-close) by bugs.debian.org; 30 Sep 2005 12:40:51 +0000
>From [EMAIL PROTECTED] Fri Sep 30 05:40:51 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1ELK3s-0006c1-00; Fri, 30 Sep 2005 05:32:24 -0700
From: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#329891: fixed in socketapi 1.7.0-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 30 Sep 2005 05:32:24 -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: socketapi
Source-Version: 1.7.0-1

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

socketapi-dev_1.7.0-1_i386.deb
  to pool/main/s/socketapi/socketapi-dev_1.7.0-1_i386.deb
socketapi1_1.7.0-1_i386.deb
  to pool/main/s/socketapi/socketapi1_1.7.0-1_i386.deb
socketapi_1.7.0-1.diff.gz
  to pool/main/s/socketapi/socketapi_1.7.0-1.diff.gz
socketapi_1.7.0-1.dsc
  to pool/main/s/socketapi/socketapi_1.7.0-1.dsc
socketapi_1.7.0.orig.tar.gz
  to pool/main/s/socketapi/socketapi_1.7.0.orig.tar.gz



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.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated socketapi 
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, 30 Sep 2005 18:59:07 +1000
Source: socketapi
Binary: socketapi1 socketapi-dev
Architecture: source i386
Version: 1.7.0-1
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description: 
 socketapi-dev - development package for socketapi1
 socketapi1 - socket API library for sctplib
Closes: 329891
Changes: 
 socketapi (1.7.0-1) unstable; urgency=low
 .
   * New upstream release.
   * Fixed "socketapi_1.3.2-2 (arm,hppa,m68k): FTBFS: internal compiler error:
     in cp_expr_size, at cp/cp-objcp-common.c:101", closes: #329891.
Files: 
 0041e86d0e16c4229da9f2e664707e0d 664 libs optional socketapi_1.7.0-1.dsc
 7e66d30efa5e3f58b300e014de15e863 503066 libs optional 
socketapi_1.7.0.orig.tar.gz
 02b66d0abe2ea086270fb52b0a3fea0f 3472 libs optional socketapi_1.7.0-1.diff.gz
 b5bb0a9894dbfe8cf59d91dd93020dd3 139666 libs optional 
socketapi1_1.7.0-1_i386.deb
 f090a4a17b6f202a3e15290ada31e33d 210946 libdevel optional 
socketapi-dev_1.7.0-1_i386.deb

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

iD8DBQFDPS8AgY5NIXPNpFURAi1qAJwMCVl23JaKqjsXTWfVNt+yRdemDACdGyHG
wXShtNSixVGYdDl1RIXDV5g=
=m6fX
-----END PGP SIGNATURE-----


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

Reply via email to