From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Noud Aldenhoven" <jwaixs@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to learn Linux Kernel Programming
Date: Wed, 22 Aug 2007 12:06:52 +0200 [thread overview]
Message-ID: <9a8748490708220306t46ed1c34m554a8df47c0794ce@mail.gmail.com> (raw)
In-Reply-To: <cb63d1e10708212347y251a34fah739c4b42ab49609e@mail.gmail.com>
(please don't trim Cc lists when replying, just use Reply-to-all)
On 22/08/07, Noud Aldenhoven <jwaixs@gmail.com> wrote:
> Thank you for your information and help,
>
> I think it's a lot more clear for me now.
> I've seen the ldd3 some time ago, but someone told me that book was
> out-of-date. Guess he was wrong.
It /is/ out of date, but it still contains a lot of useful information.
> Would it also be use full to use some
> kind of cross-compiler? (don't know if that's the right word for it)
> So I can run my stable kernel and on top of it a new experimental
> kernel where I can experiment with?
>
A cross compiler is used to compile a kernel for one architecture
while running a different one. for example; building a kernel to run
on ppc64 while running i386.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2007-08-22 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cb63d1e10708211228u383240a2l4af811f72b8858c0@mail.gmail.com>
2007-08-21 19:29 ` Noud Aldenhoven
2007-08-21 19:53 ` Rik van Riel
2007-08-22 0:48 ` Jesper Juhl
2007-08-22 3:15 ` Glauber de Oliveira Costa
[not found] ` <cb63d1e10708212346l746111dcic584b4bb5fe461fc@mail.gmail.com>
2007-08-22 6:47 ` Noud Aldenhoven
2007-08-22 9:07 ` Nicolas Vigier
2007-08-22 10:06 ` Jesper Juhl [this message]
2007-08-22 10:42 ` Bernd Petrovitsch
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=9a8748490708220306t46ed1c34m554a8df47c0794ce@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=jwaixs@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®