Your message dated Tue, 18 Oct 2005 14:26:06 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Switched back to gcc 3.4
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 07:58:52 +0000
>From [EMAIL PROTECTED] Sat Sep 24 00:58:52 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 1EJ4vs-0005iJ-00; Sat, 24 Sep 2005 00:58:52 -0700
Received: by tennyson.dodds.net (Postfix, from userid 1000)
        id 25968704E; Sat, 24 Sep 2005 00:58:51 -0700 (PDT)
Date: Sat, 24 Sep 2005 00:58:51 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: packagesearch_2.0.1 (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="82I3+IH0IqGh5yIs"
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


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

Package: packagesearch
Version: 2.0.1
Severity: serious
Justification: FTBFS

Hi Benjamin,

In addition to the PIC problem in the shared libraries, packagesearch has
failed to build on hppa with the following error, and will almost certainly
also fail to build on arm and m68k due to the same bug:

[...]
g++ -c -pipe -O2 =10kg-config --cflags libtagcoll1 libdebtags1 -D_REENTRANT=
 -Wall -W -D__DEBUG -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_GUI_LIB -DQT_XML_LIB -=
DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_SHARED -I/usr/share/qt4/mkspecs/linux=
-g++ -I. -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtXml -I/usr/incl=
ude/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I.moc -I.ui -o =
=2Eobj/runcommandinxterm.o runcommandinxterm.cpp
runcommandinxterm.cpp: In member function 'std::string NException::SimpleSt=
ring::_ZTv0_n16_NK10NException12SimpleString11descriptionEv() const':
runcommandinxterm.cpp:120: 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]: *** [.obj/runcommandinxterm.o] Error 1
make[2]: Leaving directory /build/buildd/packagesearch-2.0.1/src'
make[1]: *** [all] Error 2
[...]

A full build log can be found at
<http://buildd.debian.org/fetch.php?&pkg=3Dpackagesearch&ver=3D2.0.1&arch=
=3Dhppa&stamp=3D1127493639&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/

--82I3+IH0IqGh5yIs
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)

iD8DBQFDNQc7KN6ufymYLloRAsGVAJoDHKjrT5PKfFJ5fkAIARHrbScC2QCghfyY
Z4F/nmOP1UOmnLg3poIJNoM=
=Xtxv
-----END PGP SIGNATURE-----

--82I3+IH0IqGh5yIs--

---------------------------------------
Received: (at 329884-done) by bugs.debian.org; 18 Oct 2005 18:28:27 +0000
>From [EMAIL PROTECTED] Tue Oct 18 11:28:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from pop.gmx.de (mail.gmx.net) [213.165.64.20] 
        by spohr.debian.org with smtp (Exim 3.36 1 (Debian))
        id 1ERwCJ-0002tz-00; Tue, 18 Oct 2005 11:28:27 -0700
Received: (qmail invoked by alias); 18 Oct 2005 18:27:56 -0000
Received: from dyn-wireless-155-095.Concordia.CA (EHLO 
dyn-wireless-155-095.Concordia.CA) [132.205.155.95]
  by mail.gmx.net (mp001) with SMTP; 18 Oct 2005 20:27:56 +0200
X-Authenticated: #834378
Subject: Switched back to gcc 3.4
From: Benjamin Mesing <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Tue, 18 Oct 2005 14:26:06 -0400
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02

Thanks for the bug report!
Worked around gcc 4.0 bug on arm, hppa and m68k, by adding a rule in the
Makefile to use gcc 3.4 on arm, hppa and m68k.
The buildlog on hppa indicates, that the built fine, assuming the same
for the other architectures.

Best regards Ben





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

Reply via email to