Your message dated Mon, 26 Apr 2004 08:54:37 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#245784: Undefined u64 in jiffies.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; 25 Apr 2004 12:25:52 +0000
>From [EMAIL PROTECTED] Sun Apr 25 05:25:51 2004
Return-path: <[EMAIL PROTECTED]>
Received: from adicia.telenet-ops.be [195.130.132.56]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BHihj-0006MN-00; Sun, 25 Apr 2004 05:25:51 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
by adicia.telenet-ops.be (Postfix) with SMTP id 25927440B2
for <[EMAIL PROTECTED]>; Sun, 25 Apr 2004 14:25:50 +0200 (MEST)
Received: from kabel.telenet.be (D5767DEE.kabel.telenet.be [213.118.125.238])
by adicia.telenet-ops.be (Postfix) with ESMTP id 0E0E344075
for <[EMAIL PROTECTED]>; Sun, 25 Apr 2004 14:25:50 +0200 (MEST)
Received: by kabel.telenet.be (Postfix, from userid 501)
id 8133A158AD5; Sun, 25 Apr 2004 14:25:49 +0200 (CEST)
Date: Sun, 25 Apr 2004 14:25:49 +0200
From: Kurt Roeckx <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Undefined u64 in jiffies.h.
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Sender: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.5 required=4.0 tests=BAYES_01,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
X-CrossAssassin-Score: 1
Package: linux-kernel-headers
Version: 2.5.999-test7-bk-15
In /usr/include/linux/jiffies.h line 16, 20 and 22 it uses the
u64 type. That type is __KERNEL__ only.
I think the whole file should be probably be #ifdef'd to
__KERNEL__ but I'm not sure.
This problem causes a build failure for sysklogd and should
therefor probably be tagged as RC.
Kurt
---------------------------------------
Received: (at 245784-done) by bugs.debian.org; 25 Apr 2004 23:54:39 +0000
>From [EMAIL PROTECTED] Sun Apr 25 16:54:39 2004
Return-path: <[EMAIL PROTECTED]>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BHtSJ-000285-00; Sun, 25 Apr 2004 16:54:39 -0700
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
by webmasters.gr.jp (Postfix) with ESMTP
id C1911DEB58; Mon, 26 Apr 2004 08:54:37 +0900 (JST)
Date: Mon, 26 Apr 2004 08:54:37 +0900
Message-ID: <[EMAIL PROTECTED]>
From: GOTO Masanori <[EMAIL PROTECTED]>
To: Kurt Roeckx <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Cc: GOTO Masanori <[EMAIL PROTECTED]>
Subject: Re: Bug#245784: Undefined u64 in jiffies.h.
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
(i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
X-CrossAssassin-Score: 1
At Sun, 25 Apr 2004 16:44:42 +0200,
Kurt Roeckx wrote:
> On Sun, Apr 25, 2004 at 11:21:53PM +0900, GOTO Masanori wrote:
> >
> > Which version did you build sysklogd ?
>
> I'm using 1.4.1-10, which is the latest in testing.
>
> Trying the same with 1.4.1-14 fixes all my problems.
>
> Sorry for all those bugreports about sysklogd.
OK... I've closed them. But if you think some headers are still
broken on the current sid, please reopen and report us.
Regards,
-- gotom
