From: Mitch <Mitch@0Bits.COM>
To: jdike@addtoit.com, linux-kernel@vger.kernel.org
Subject: Re: UML build failure with 2.6.18
Date: Wed, 20 Sep 2006 19:31:19 +0400 [thread overview]
Message-ID: <45115EC7.2010407@0Bits.COM> (raw)
It's no distro (built up myself, so you can assume a gentoo type build).
I'm building from scratch, so it should use no headers since i'm
building a kernel.
-------- Original Message --------
Subject: Re: UML build failure with 2.6.18
Date: Wed, 20 Sep 2006 11:22:57 -0400
From: Jeff Dike <jdike@addtoit.com>
To: Mitch@0Bits.COM
CC: linux-kernel@vger.kernel.org
References: <Pine.LNX.4.63.0609201724320.29128@hasbox.com>
On Wed, Sep 20, 2006 at 05:27:12PM +0400, Mitch@0Bits.COM wrote:
> anyone having UML build failure with the shiny new 2.6.18
> CC arch/um/os-Linux/process.o
> arch/um/os-Linux/process.c:144: error: syntax error before 'getpid'
> arch/um/os-Linux/process.c:146: warning: return type defaults to 'int'
> arch/um/os-Linux/process.c:146: warning: function declaration isn't a
> prototype
> arch/um/os-Linux/process.c: In function '_syscall0':
> arch/um/os-Linux/process.c:147: error: syntax error before '{' token
> arch/um/os-Linux/process.c:162: error: syntax error before 'prot'
> arch/um/os-Linux/process.c:209: error: parameter 'ok' is initialized
> arch/um/os-Linux/process.c:211: error: syntax error before 'printk'
> arch/um/os-Linux/process.c:279: error: syntax error before '*' token
> make[1]: *** [arch/um/os-Linux/process.o] Error 1
> make: *** [arch/um/os-Linux] Error 2
What's the host distro?
I just built (plus the jmmpbuf patch, which isn't the problem here)
and booted it, and it seems fine here.
Jeff
next reply other threads:[~2006-09-20 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 15:31 Mitch [this message]
2006-09-20 16:47 ` UML build failure with 2.6.18 Bill Rugolsky Jr.
2006-09-20 17:40 ` Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2006-09-20 21:05 Mitch
2006-09-20 13:27 Mitch
2006-09-20 15:22 ` Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45115EC7.2010407@0Bits.COM \
--to=mitch@0bits.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.