From: Kent Borg <kentborg@borg•org>
To: Embedded Linux PPC List <linuxppc-embedded@lists•linuxppc.org>
Subject: Compile Penguin PPC for x386?
Date: Wed, 12 Dec 2001 16:58:19 -0500 [thread overview]
Message-ID: <20011212165819.D1790@borg.org> (raw)
Is the i386 arch vaguely up to date in the PPC tree? Does it work?
I mean, if I want to debug some driver that doesn't need actual
hardware (maybe dummy out actual HW banging), can I swap over to
building an i386 kernel? It would be nice to be using the same
kernel.
If I can do that, how? In Makefile I changed "ARCH" to i386, changed
"CROSS_COMPILE" to be nothing, did a "make mrproper", copied in a
.config from my Red Hat install, defaulted everything asked by "make
oldconfig", did "make dep", and "make bzImage".
But then it chokes on some problem in include/linux/highmem.h (48:
parse error before `0').
Should this work?
Thanks,
-kb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-12-12 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 21:58 Kent Borg [this message]
2001-12-12 19:21 ` Compile Penguin PPC for x386? Matt Porter
2001-12-20 10:57 ` Marius Groeger
2001-12-20 11:12 ` Matt Porter
2001-12-13 0:13 ` andrew may
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=20011212165819.D1790@borg.org \
--to=kentborg@borg$(echo .)org \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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