From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] cris
Date: Mon, 23 Jun 2008 15:03:23 +0200 [thread overview]
Message-ID: <20080623130323.GB8920@mx.loc> (raw)
In-Reply-To: <485F507D.5070801@cetrtapot.si>
On Mon, Jun 23, 2008 at 09:27:57AM +0200, Hinko Kocevar wrote:
>Bernhard Fischer wrote:
>>> +ifeq ($(BR2_ARCH),"cris")
>>> + cp -a $(LINUX_HEADERS_UNPACK_DIR)/include/linux/user.h $(LINUX_HEADERS_DIR)/include/linux
>>> + cp -a $(LINUX_HEADERS_UNPACK_DIR)/include/asm-cris/user.h $(LINUX_HEADERS_DIR)/include/asm
>>> + cp -a $(LINUX_HEADERS_UNPACK_DIR)/include/asm-cris/elf.h $(LINUX_HEADERS_DIR)/include/asm
>>> + cp -a $(LINUX_HEADERS_UNPACK_DIR)/include/asm-cris/arch-v10 $(LINUX_HEADERS_DIR)/include/asm/arch
>>> + sed -i -e "/^#include <asm\/page\.h>/d" $(LINUX_HEADERS_DIR)/include/asm/user.h
>>
>> as you can see this wouldn't work for v8 and generally should be fixed
>> in the kernel (also fails with 2.6.git).
>
>This problem is because include/asm-cris/Kbuild does not include the correct headers when the kernel source is not configured. Both include/asm-cris/arch-vXX directories are left behind when install_headers goes through header-y target.
>
>I'll let Axis people sort it out (if ever), till then I guess we are stuck with the hack..
Yes, we'd need to use a prepared kernel ("archprepare"), which means
dropping the one from tool_build and setting one up early in project_.
I currently don't have time to do this properly, perhaps you want to
give it a try?
next prev parent reply other threads:[~2008-06-23 13:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 10:23 [Buildroot] GIT or SVN Hinko Kocevar
2008-06-19 10:53 ` Hinko Kocevar
2008-06-19 11:13 ` Bernhard Fischer
2008-06-19 11:54 ` Hinko Kocevar
2008-06-19 12:03 ` Bernhard Fischer
2008-06-19 12:20 ` Hinko Kocevar
2008-06-19 13:25 ` Hinko Kocevar
2008-06-19 19:09 ` Peter Korsgaard
2008-06-20 8:36 ` Bernhard Fischer
2008-06-20 8:40 ` Hinko Kocevar
2008-06-20 12:57 ` Bernhard Fischer
2008-06-20 13:15 ` Hinko Kocevar
2008-06-20 13:24 ` Bernhard Fischer
2008-06-23 10:10 ` Hinko Kocevar
2008-06-20 13:26 ` Hinko Kocevar
2008-06-20 14:11 ` [Buildroot] cris Bernhard Fischer
2008-06-20 14:30 ` Peter Korsgaard
2008-06-20 15:03 ` Bernhard Fischer
2008-06-23 7:27 ` Hinko Kocevar
2008-06-23 8:50 ` Hinko Kocevar
2008-06-23 13:06 ` Bernhard Fischer
2008-06-23 14:48 ` Hinko Kocevar
2008-06-23 13:03 ` Bernhard Fischer [this message]
2008-06-23 14:41 ` Hinko Kocevar
2008-06-23 14:46 ` Bernhard Fischer
2008-06-23 14:54 ` Hinko Kocevar
2008-06-23 15:01 ` Bernhard Fischer
2008-07-30 2:39 ` Ralph Siemsen
2008-06-20 13:18 ` [Buildroot] GIT or SVN Peter Korsgaard
2008-07-30 8:20 ` Hinko Kocevar
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=20080623130323.GB8920@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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