Your message dated Wed, 28 Sep 2005 22:44:50 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#330101: gcc-4.0: ftbfs [sparc] make[2]: *** No rule to
make target `current_symbols.txt'
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; 25 Sep 2005 23:16:28 +0000
>From [EMAIL PROTECTED] Sun Sep 25 16:16:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from blars.org (renig.nat.blars.org) [64.81.35.59]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EJfjO-0004gk-00; Sun, 25 Sep 2005 16:16:27 -0700
Received: from quaff (quaff.nat.blars.org [172.16.2.7])
by renig.nat.blars.org (8.13.4/8.13.4/Debian-3) with ESMTP id
j8PNGApx003114
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Sun, 25 Sep 2005 16:16:12 -0700
Received: from quaff.nat.blars.org (quaff [127.0.0.1])
by quaff (8.13.5/8.13.5/Debian-1) with ESMTP id j8PNc4EV028011;
Sun, 25 Sep 2005 16:38:04 -0700
Received: (from [EMAIL PROTECTED])
by quaff.nat.blars.org (8.13.5/8.13.5/Submit) id j8PNc4nO028009;
Sun, 25 Sep 2005 16:38:04 -0700
Date: Sun, 25 Sep 2005 16:38:04 -0700
From: Blars Blarson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc-4.0: ftbfs [sparc] make[2]: *** No rule to make target
`current_symbols.txt'
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.17
User-Agent: Mutt/1.5.10i
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
Package: gcc-4.0
Version: 4.0.1-9
Severity: serious
Justification: fails to build from source
gcc-4.0 failed to build on a sparc buildd, but succeeded on my sparc
pbuilder. Possible reasons for this include timestamp scew, more
recent kernel version on my pbuilder, and more recent
build-dependancies.
cat debian/README.libstdc++-baseline.in \
> debian/README.libstdc++-baseline
baseline_name=`basename
/build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu`; \
baseline_parentdir=`dirname
/build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu`; \
compat_baseline_name=""; \
if [ -f
"/build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu/baseline_symbols.txt"
]; then \
( \
echo "A baseline file for $baseline_name was found."; \
echo "Running the check-abi script ..."; \
echo ""; \
/usr/bin/make -C
/build/buildd/gcc-4.0-4.0.1/build/sparc-linux-gnu/libstdc++-v3/testsuite \
check-abi; \
) >> debian/README.libstdc++-baseline; \
else \
( \
echo "No baseline file found for $baseline_name."; \
echo "Generating a new baseline file ..."; \
echo ""; \
) >> debian/README.libstdc++-baseline; \
mkdir
/build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu; \
/usr/bin/make -C
/build/buildd/gcc-4.0-4.0.1/build/sparc-linux-gnu/libstdc++-v3/testsuite
new-abi-baseline; \
cat
/build/buildd/gcc-4.0-4.0.1/src/libstdc++-v3/config/abi/sparc-linux-gnu/baseline_symbols.txt
>> debian/README.libstdc++-baseline; \
fi
make[2]: *** No rule to make target `current_symbols.txt', needed by
`check-abi'. Stop.
make[1]: *** [debian/README.libstdc++-baseline] Error 2
make[1]: Leaving directory `/build/buildd/gcc-4.0-4.0.1'
make: *** [binary-arch] Error 2
---------------------------------------
Received: (at 330101-done) by bugs.debian.org; 28 Sep 2005 20:44:58 +0000
>From [EMAIL PROTECTED] Wed Sep 28 13:44:58 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EKinS-0000gS-00; Wed, 28 Sep 2005 13:44:58 -0700
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id WAA25622;
Wed, 28 Sep 2005 22:44:52 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 5370BF20F;
Wed, 28 Sep 2005 22:44:52 +0200 (MEST)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
id 02582-20; Wed, 28 Sep 2005 22:44:50 +0200 (MEST) 11326
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
Wed, 28 Sep 2005 22:44:50 +0200 (MEST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j8SKiosE005639;
Wed, 28 Sep 2005 22:44:50 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 28 Sep 2005 22:44:50 +0200
To: Blars Blarson <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#330101: gcc-4.0: ftbfs [sparc] make[2]: *** No rule to make
target `current_symbols.txt'
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
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
Blars Blarson writes:
> Package: gcc-4.0
> Version: 4.0.1-9
> Severity: serious
> Justification: fails to build from source
>
> gcc-4.0 failed to build on a sparc buildd, but succeeded on my sparc
> pbuilder. Possible reasons for this include timestamp scew, more
> recent kernel version on my pbuilder, and more recent
> build-dependancies.
no, no pty's available. closing this report, this is not package
specific, and we don't have a buildd pseudo package for submitting bug
reports.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
