Your message dated 30 Aug 2003 12:55:10 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#203180: [Fwd: Re: base: error in /usr/include/sched.h]
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; 28 Jul 2003 09:46:18 +0000
>From [EMAIL PROTECTED] Mon Jul 28 04:46:15 2003
Return-path: <[EMAIL PROTECTED]>
Received: from static-ctb02118.webone.com.au (sun) [210.9.242.118]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19h4a6-0007Aq-00; Mon, 28 Jul 2003 04:46:15 -0500
Received: from jim by sun with local (Exim 3.36 #1 (Debian))
id 19h4a1-0007u2-00; Mon, 28 Jul 2003 19:46:09 +1000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jim Watson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: base: error in /usr/include/sched.h
X-Mailer: reportbug 2.20
Date: Mon, 28 Jul 2003 19:46:08 +1000
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-6.0 required=4.0
tests=BAYES_10,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20
(1.174.2.15-2003-03-30-exp)
Package: base
Version: unavailable; reported 2003-07-28
Severity: important
Tags: patch
-- System Information:
Debian Release: testing/unstable
Architecture: sparc
Kernel: Linux sun 2.4.18 #1 SMP Mon Jan 27 14:07:39 EST 2003 sparc64
Locale: LANG=C, LC_CTYPE=en_US.UTF-8
building module goodies with gcc-3.2.3 there are various errors around line
76
of /usr/include/sched.h - (it cannot be build with gcc-3.3.1 yet.)
this can be fixed as follows in sched.h
/* Set the CPU affinity for a task */
extern int sched_setaffinity (__pid_t __pid, __const cpu_set_t *__mask)
__THROW;
^^^^
put it all into one line
extern int sched_setaffinity (__pid_t __pid, __const cpu_set_t *__mask)__THROW;
---------------------------------------
Received: (at 203180-done) by bugs.debian.org; 30 Aug 2003 10:55:18 +0000
>From [EMAIL PROTECTED] Sat Aug 30 05:55:16 2003
Return-path: <[EMAIL PROTECTED]>
Received: from pc2-cmbg4-3-cust239.cmbg.cable.ntl.com (kc.cam.armlinux.org)
[81.96.69.239]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19t3O0-0006yu-00; Sat, 30 Aug 2003 05:55:16 -0500
Received: from localhost ([127.0.0.1])
by kc.cam.armlinux.org with esmtp (Exim 3.36 #1 (Debian))
id 19t4K1-0000Cq-00; Sat, 30 Aug 2003 12:55:13 +0100
Subject: Re: Bug#203180: [Fwd: Re: base: error in /usr/include/sched.h]
From: Philip Blundell <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Content-Type: text/plain
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.3
Date: 30 Aug 2003 12:55:10 +0100
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-14.5 required=4.0
tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_XIMIAN
autolearn=ham version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_27
(1.174.2.15-2003-03-30-exp)
On Sat, 2003-08-30 at 03:55, Jim Watson wrote:
> I am sorry - i cannot reproduce this now, i have gone to gcc-3.3 ,
> but the whitespace is is still there in sched.h,
> i just recompiled the "problem" source with no errors
> i cannot explain now why this occurred.
>
> something did happen that led me to line 76 of sched.h,
> but now it is "unreproducable"
>
> sorry to waste time
Okay, thanks for letting me know. I'm closing this bug, since it sounds
like there is nothing we can do. If the problem recurs, please reopen
it or file a new report.
p.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
