[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#270856: marked as done (parse error when compiling against '/usr/include/asm/sigcontext.h')



Your message dated Sat, 28 May 2005 09:25:07 +0900
with message-id <8164x419jw.wl@omega.webmasters.gr.jp>
and subject line Bug#270856: parse error when compiling against '/usr/include/asm/sigcontext.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; 9 Sep 2004 16:39:12 +0000
>From paulcboyle@gmail.com Thu Sep 09 09:39:12 2004
Return-path: <paulcboyle@gmail.com>
Received: from rproxy.gmail.com (mproxy.gmail.com) [64.233.170.198] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1C5Rx2-0008HM-00; Thu, 09 Sep 2004 09:39:12 -0700
Received: by mproxy.gmail.com with SMTP id v18so320511rnb
        for <submit@bugs.debian.org>; Thu, 09 Sep 2004 09:39:03 -0700 (PDT)
Received: by 10.38.11.80 with SMTP id 80mr277054rnk;
        Thu, 09 Sep 2004 09:38:55 -0700 (PDT)
Received: by 10.38.8.35 with HTTP; Thu, 9 Sep 2004 09:38:54 -0700 (PDT)
Message-ID: <2595c57b040909093839b8b81c@mail.gmail.com>
Date: Thu, 9 Sep 2004 17:38:54 +0100
From: Paul Boyle <paulcboyle@gmail.com>
Reply-To: Paul Boyle <paulcboyle@gmail.com>
To: submit@bugs.debian.org
Subject: parse error when compiling against '/usr/include/asm/sigcontext.h'
Cc: debian-glibc@lists.debian.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

package: linux-kernel-header
version:2.5.99

There appears to be a parse error in one of the header files
associated with this package. It is difficult to believe that this has
not been noticed before, but I can't seem to find it on the debian bug
lists.

In the file '/usr/include/asm/sigcontext.h' there appears to be a
problem with line 79.

78:        unsigned short ss, __ssh;
79:        struct _fpstate __user * fpstate;
80:        unsigned long oldmask;

When compiling programs that are linked against this file, I get a
parse error on line 79. But if I change the line to the following

'79:         struct _fpstate * fpstate; '

the parse error disappears and everything works fine.

I have checked on google and this problem is mentioned several times
as being a debian specific bug, but I can not find any mention of it
on any debian bug list or mailing list.

I have noted that on a gentoo system that I have access to, the line
reads as I have it above, i.e. the modified line.

I have my computer upto date with debian 'testing' and  I have a
non-debian vanilla  kernel  2.4.26 installed. With the exception of
the kernel everything is standard debian.

Paul

---------------------------------------
Received: (at 270856-done) by bugs.debian.org; 28 May 2005 00:25:08 +0000
>From gotom@debian.or.jp Fri May 27 17:25:08 2005
Return-path: <gotom@debian.or.jp>
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 1Dbp8W-00026Q-00; Fri, 27 May 2005 17:25:08 -0700
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
	by webmasters.gr.jp (Postfix) with ESMTP id 63BD4DEB1E
	for <270856-done@bugs.debian.org>; Sat, 28 May 2005 09:25:07 +0900 (JST)
Date: Sat, 28 May 2005 09:25:07 +0900
Message-ID: <8164x419jw.wl@omega.webmasters.gr.jp>
From: GOTO Masanori <gotom@debian.or.jp>
To: 270856-done@bugs.debian.org
Subject: Re: Bug#270856: parse error when compiling against '/usr/include/asm/sigcontext.h'
In-Reply-To: <81zn3tpqkx.wl@omega.webmasters.gr.jp>
References: <2595c57b040913041319c3adbd@mail.gmail.com>
	<81zn3tpqkx.wl@omega.webmasters.gr.jp>
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: 270856-done@bugs.debian.org
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-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
X-Spam-Level: 

At Tue, 14 Sep 2004 10:49:34 +0900,
GOTO Masanori wrote:
> At Mon, 13 Sep 2004 12:13:52 +0100,
> Paul Boyle wrote:
> > I have tried to compile the following program
> > 
> > #include <asm/sigcontext.h>
> > int main()
> > {
> > return 0;
> > }
> > 
> > When I try to compile this I get the following parse errors
> > 
> > /usr/include/asm/sigcontext.h:79: error: parse error before '*' token
> > /usr/include/asm/sigcontext.h:82: error: parse error before '}' token
> > 
> > But if I remove the "__user" from sigcontext.h everything work okay.
> > 
> > Here is a brief list of the package versions installed on my computer.
> > 
> > gcc  3.3.4
> > libc6 2.3.2
> > kernel 2.4.26
> 
> Which architecture did you use?  If i386, then it should not be occured.
> 
> > With the exception of the kernel, which I compiled myself,  everything
> > else is pure debian with no special configuration. I have kept the
> > system up to date with testing.
> 
> Try to reinstall linux-kernel-headers.  I guess you may overwrite
> linux dir when you install your kernel.

This report was left opening over half of year, but it worked nicely.
I close it.  Paul, if you still have problem, please let us know and
reopen with your trouble description.

Regards,
-- gotom



Reply to: