From: Chen Gang <gang.chen@asianux.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tony Breeds <tony@bakeyournoodle.com>,
Mark Salter <msalter@redhat.com>,
"a-jacquiot@ti.com" <a-jacquiot@ti.com>,
jkc@redhat.com, linux-c6x-dev@linux-c6x.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] arch: c6x: kernel: include "linux/console.h" when 'VT' and 'DUMMY_CONSOLE' enabled.
Date: Tue, 25 Jun 2013 15:34:21 +0800 [thread overview]
Message-ID: <51C947FD.4000205@asianux.com> (raw)
In-Reply-To: <CAMuHMdXngNACn+Qfw1ytJkWWLm_BC+g_PTDpHHbUQyeeyVu8Fg@mail.gmail.com>
On 06/25/2013 03:06 PM, Geert Uytterhoeven wrote:
> On Tue, Jun 25, 2013 at 3:58 AM, Chen Gang <gang.chen@asianux.com> wrote:
>> > Need include "linux/console.h" when 'VT' and 'DUMMY_CONSOLE' enabled
>> > (e.g allmodconfig).
>> >
>> > The related error:
>> > arch/c6x/kernel/setup.c: In function ‘setup_arch’:
>> > arch/c6x/kernel/setup.c:442:2: error: ‘conswitchp’ undeclared (first use in this function)
>> > arch/c6x/kernel/setup.c:442:2: note: each undeclared identifier is reported only once for each function it appears in
>> > arch/c6x/kernel/setup.c:442:16: error: ‘dummy_con’ undeclared (first use in this function)
> Ah, so you managed to obtain a c6x toolchain. There's none at
> https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/ yet :-(
Hmm..., I use:
[root@dhcp122 linux-next]# rpm -qf /usr/bin/c6x-linux-gnu-gcc
gcc-c6x-linux-gnu-4.7.1-0.1.20120606.fc17.x86_64
When fix the 3 compiling issues, it almost can pass compiling: during
compiled to fs subsystem, I stopped compilation manually.
Thanks.
--
Chen Gang
Asianux Corporation
prev parent reply other threads:[~2013-06-25 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 1:58 [PATCH] arch: c6x: kernel: include "linux/console.h" when 'VT' and 'DUMMY_CONSOLE' enabled Chen Gang
2013-06-25 7:06 ` Geert Uytterhoeven
2013-06-25 7:34 ` Chen Gang [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=51C947FD.4000205@asianux.com \
--to=gang.chen@asianux.com \
--cc=a-jacquiot@ti.com \
--cc=geert@linux-m68k.org \
--cc=jkc@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
--cc=tony@bakeyournoodle.com \
/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