From: Dan Kegel <dank@kegel.com>
To: geert@linux-m68k.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Getting kernel.org kernel to build for m68k?
Date: Tue, 31 Aug 2004 22:35:04 -0700 [thread overview]
Message-ID: <41355F88.2080801@kegel.com> (raw)
Hi Geert,
I see from
http://linux-m68k-cvs.apia.dhs.org/~geert/linux-m68k-2.6.x-merging/
that you're merging patches back into Linus' kernel. Great!
I noticed today that Linus's m68k kernel can't be built (at least with gcc-3.4.1).
The first problem I ran into,
CC arch/m68k/kernel/asm-offsets.s
In file included from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/m68k/kernel/asm-offsets.c:12:
include/linux/thread_info.h:30: error: parse error before '{' token
is solved already in the m68k tree.
(In particular,
the #ifndef __HAVE_THREAD_FUNCTIONS ... #endif in
http://linux-m68k-cvs.apia.dhs.org/c/cvsweb/linux/include/linux/thread_info.h?rev=1.5;content-type=text%2Fplain
probably solves it.)
There are other problems after that.
Any chance you could spend a bit of time sending Linus enough
patches for his kernel to build for m68k, if not run?
It would be helpful to my crosstool project (I'm adding a
"can this toolchain build the kernel" test, and it's a lot
easier if I can count on the kernel.org tree at least building).
Thanks,
Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
next reply other threads:[~2004-09-01 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 5:35 Dan Kegel [this message]
2004-09-01 8:36 ` Getting kernel.org kernel to build for m68k? Geert Uytterhoeven
2004-09-05 10:41 ` Geert Uytterhoeven
2004-09-05 11:01 ` Matthias Urlichs
2004-09-05 11:03 ` Christoph Hellwig
2004-09-05 13:19 ` Matthias Urlichs
2004-09-05 13:49 ` Christoph Hellwig
2004-09-05 15:45 ` Roman Zippel
2004-09-05 15:48 ` Matthias Urlichs
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=41355F88.2080801@kegel.com \
--to=dank@kegel.com \
--cc=geert@linux-m68k.org \
--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.