Your message dated Wed, 25 Apr 2001 22:25:39 +0200 (MEST)
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-2.95.4-0.010425
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.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Apr 2001 07:19:39 +0000
>From [EMAIL PROTECTED] Mon Apr 16 02:19:39 2001
Return-path: <[EMAIL PROTECTED]>
Received: from cr499794-a.crdva1.bc.wave.home.com (oasis.zugzug.com)
[24.113.91.74] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14p3IR-00009V-00; Mon, 16 Apr 2001 02:19:39 -0500
Received: (from [EMAIL PROTECTED])
by oasis.zugzug.com (8.12.0.Beta5/8.12.0.Beta5/Debian 8.12.0-1) id
f3G7JbxU000536;
Mon, 16 Apr 2001 00:19:37 -0700
Message-Id: <[EMAIL PROTECTED]>
From: Jeff Bailey <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: debian/rules2 contains Linuxism
X-Reportbug-Version: 1.14
X-Mailer: reportbug 1.14
Date: Mon, 16 Apr 2001 00:19:37 -0700
Delivered-To: [EMAIL PROTECTED]
Package: gcc-2.95
Severity: important
The testsuite in rules2 (appears twice) does:
+ -echo "Running testsuite ..."; \
+ m=`awk '/^((Mem|Swap)Free|Cached)/{m+=$$2}END{print int(m*.9)}' \
+ /proc/meminfo`; \
+ ulimit -m $$m; \
+ echo "Limited memory for test runs to `ulimit -m`kB"; \
+ $(MAKE) -C $(builddir) -k check 2>&1 | tee test-protocol
There is no proc filesystem on the Hurd.
Is the ulimit critical to the test suite? If not, can you wrap the 'awk' and
'ulimit' lines with
ifneq ($(DEB_HOST_ARCH),hurd-i386)
m=`awk '/^((Mem|Swap)Free|Cached)/{m+=$$2}END{print int(m*.9)}' \
/proc/meminfo`; \
ulimit -m $$m;
endif
You may want to approach this a different way, since this makes "Linux" the
norm, and "Hurd" the deviant. It would probably be better to test if
the DEB_HOST_ARCH were a member of the "Linux" family. I don't know a
good way to do this (Please let me know if you do, it will be useful to
me elsewhere!)
-- System Information
Debian Release: testing/unstable
Architecture: hurd-i386
---------------------------------------
Received: (at 94127-done) by bugs.debian.org; 25 Apr 2001 20:31:19 +0000
>From [EMAIL PROTECTED] Wed Apr 25 15:31:19 2001
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14sVwV-0005OP-00; Wed, 25 Apr 2001 15:31:19 -0500
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id WAA24598;
Wed, 25 Apr 2001 22:25:40 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.9.3+Sun/8.9.3) id WAA06338;
Wed, 25 Apr 2001 22:25:40 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 25 Apr 2001 22:25:39 +0200 (MEST)
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: fixed in gcc-2.95.4-0.010425
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
gcc-2.95 (2.95.4.ds1-0.010424) unstable; urgency=high
* Apply updated ppc-fsirl patch (function.c removed) for all archs again.
urgency=high for powerpc.
* Remove patches included in ppc-fsirl patch: ppc-descriptions, ppc-ice.
* Correct build dependency (hurd-i386) (#94038).
* debian/rules2: Get free memory correctly on hurd (#94127).
* close #68452: ash is available on sparc and doesn't have any
special build rules for sparc.
* close #79882: bind-8.2.3 compiles fine on i386.
* Alpha related bug fixed in 2.95.3 (closes #94137).
* Fix typo in docs (-fstdc -> -stdc). Closes #94894, #94899.
* Not a bug: #93481 (see report).
