From: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
To: linux-sh@vger.kernel.org
Subject: Re: build breakage sh in next
Date: Fri, 25 Mar 2011 12:59:07 +0000 [thread overview]
Message-ID: <AANLkTimiK4ntxJG5NJ-4q7WQm6DdM7drargXSmGjCFyy@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1103250844300.22824@axis700.grange>
Hi,
2011/3/25 Guennadi Liakhovetski <g.liakhovetski@gmx.de>:
> /opt/src/linux-2.6/arch/sh/kernel/process.c: In function 'alloc_thread_info':
> /opt/src/linux-2.6/arch/sh/kernel/process.c:67: error: 'node' undeclared (first use in this function)
> /opt/src/linux-2.6/arch/sh/kernel/process.c:67: error: (Each undeclared identifier is reported only once
> /opt/src/linux-2.6/arch/sh/kernel/process.c:67: error: for each function it appears in.)
> make[2]: *** [arch/sh/kernel/process.o] Error 1
> make[1]: *** [arch/sh/kernel] Error 2
> make: *** [sub-make] Error 2
This already revised by patch of "[PATCH] sh: Fix build
alloc_thread_info_node function".
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
prev parent reply other threads:[~2011-03-25 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 7:45 build breakage sh in next Guennadi Liakhovetski
2011-03-25 12:59 ` Nobuhiro Iwamatsu [this message]
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=AANLkTimiK4ntxJG5NJ-4q7WQm6DdM7drargXSmGjCFyy@mail.gmail.com \
--to=iwamatsu@nigauri.org \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).