From: Guenter Roeck <linux@roeck-us.net>
To: Chen Gang <gang.chen@asianux.com>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] h8300/kernel/setup.c: add "linux/initrd.h" to pass compiling
Date: Fri, 30 Aug 2013 04:18:12 -0700 [thread overview]
Message-ID: <52207F74.6000702@roeck-us.net> (raw)
In-Reply-To: <52203CF0.5040600@asianux.com>
On 08/29/2013 11:34 PM, Chen Gang wrote:
> On 08/30/2013 12:53 PM, Guenter Roeck wrote:
>> On 08/29/2013 08:59 PM, Chen Gang wrote:
>>> The related error (allmodconfig for h8300):
>>>
>>> arch/h8300/kernel/setup.c: In function 'setup_arch':
>>> arch/h8300/kernel/setup.c:103:3: error: 'initrd_start' undeclared
>>> (first use in this function)
>>> initrd_start = memory_start;
>>> ^
>>> arch/h8300/kernel/setup.c:103:3: note: each undeclared identifier
>>> is reported only once for each function it appears in
>>> arch/h8300/kernel/setup.c:104:3: error: 'initrd_end' undeclared
>>> (first use in this function)
>>> initrd_end = memory_start += be32_to_cpu(((unsigned long *)
>>> (memory_start))[2]);
>>> ^
>>>
>>> Signed-off-by: Chen Gang <gang.chen@asianux.com>
>>> ---
>>
>> Maybe an odd question, but is there a way to actually compile the h8300
>> target
>
> Firstly, at least for me, I don't think it is an odd question. :-)
>
> For the tool-chain:
>
> I compiled the cross-compiler from the gcc and binutils source code.
> GCC has too many bugs to compile kernel with -Os (normal make will fail).
> If without -Os (no optimization), it can work correctly which is enough for my goal: "let h8300 pass allmodconfig". ;-)
>
>>From building with allmodconfig for h8300:
>
> I can find more chances to provide contributes (both for h8300 and for others).
> I can learn more in kernel wide.
> I can familiar the gcc and binutils step by step (especially to familiar with their issues).
>
> Next:
>
> I will communicate/work with the gcc guys for the gcc issues which found by building kernel.
>
> :-)
>
>
>
>> in the first place ? The cross compiler on kernel.org doesn't work, nor
>> does
>> the one available through Ubuntu.
>>
>> Guenter
>>
>
> For binutils, no release under Ubuntu, and the Fedora17's is incorrect
> (can not use), but the binutils-2.22 from gnu is OK.
>
> For gcc, no release under Ubuntu, for Fedora17's, gcc-4.9, gcc-4.8,
> gcc-4.7.4, and gcc-4.4.7 all have bugs for compiling kernel(their bugs
> are different too).
>
> It is really not easy to fix these bugs (gcc guys have too many issues
> to fix), even if really find the root cause, it is still difficult to
> fix (fix one bug is very easy to cause another more issues).
>
I have to wonder ... is this all worth it ? It almost looks like no one
is using this architecture anymore. Do you have target hardware to test
any of your changes ?
Thanks,
Guenter
next prev parent reply other threads:[~2013-08-30 11:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 10:31 [PATCH] h8300/kernel/setup.c: add "linux/initrd.h" to pass compiling Chen Gang
2013-08-26 11:00 ` Geert Uytterhoeven
2013-08-26 11:06 ` Chen Gang
2013-08-26 11:08 ` Geert Uytterhoeven
2013-08-26 11:19 ` Chen Gang
2013-08-26 22:12 ` Guenter Roeck
2013-08-27 1:58 ` Chen Gang
2013-08-30 3:54 ` Chen Gang
2013-08-30 3:59 ` [PATCH v2] " Chen Gang
2013-08-30 4:32 ` Guenter Roeck
2013-08-30 5:49 ` Chen Gang
2013-08-30 11:12 ` Guenter Roeck
2013-09-02 2:51 ` Chen Gang
2013-08-30 4:53 ` Guenter Roeck
2013-08-30 6:34 ` Chen Gang
2013-08-30 11:18 ` Guenter Roeck [this message]
2013-08-30 11:44 ` richard -rw- weinberger
2013-08-30 12:20 ` Guenter Roeck
2013-09-02 3:26 ` Chen Gang
2013-09-03 8:29 ` [PATCH trivial] block/ioctl.c: let code match 'kernel code style' Chen Gang
2013-09-03 8:55 ` Li Zefan
2013-09-03 9:06 ` Chen Gang
2013-09-03 9:27 ` Jiri Kosina
2013-09-03 9:58 ` Chen Gang
2013-09-03 9:54 ` Chen Gang
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=52207F74.6000702@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gang.chen@asianux.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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