From: Russell King <rmk@arm.linux.org.uk>
To: cyt@liih.org (Yin Tan Cui)
Cc: gregg_99@mailcity.com, linux-kernel@vger.kernel.org
Subject: Re: Cannot compile my kernel due to unpredictible situations:
Date: Fri, 12 Jan 2001 11:34:13 +0000 (GMT) [thread overview]
Message-ID: <200101121134.f0CBYDB04046@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.30.0101121039590.1542-100000@flash.liih.org> from "Yin Tan Cui" at Jan 12, 2001 10:45:19 AM
Here are three golden rules of unpacking a kernel tarball:
1. Make sure that you have sufficient free space on the partition before
unpacking.
Reason: the kernel source is not small. Currently the 2.4.0 kernel is
around 105MB, but once built it will grow to 125MB or more depending on
your configuration.
2. Make sure that there isn't a pre-existing file or directory called 'linux'
Reason: unpacking a new kernel tree over an old kernel tree will give
unpredicatable results, and may end up with it failing to build, or
failing to unpack if 'linux' is a file.
3. Never unpack a kernel tar ball in /usr/src
Reason: some systems still have symlinks from /usr/include/linux into
/usr/src/linux/include/linux. The headers in /usr/include/linux are
supposed to be the ones that your C library was compiled against, not
the current kernel you are running.
Suggestion: create a directory called '/usr/src/v2.4.0' and unpack in
there. If you need any extra patches, or other utilities (eg, modutils)
you have a convienient place to keep them for later reference.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-12 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 23:30 Cannot compile my kernel due to unpredictible situations: Gregg Lloyd
2001-01-11 23:44 ` J . A . Magallon
2001-01-11 23:45 ` Yin Tan Cui
2001-01-12 11:34 ` Russell King [this message]
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=200101121134.f0CBYDB04046@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cyt@liih.org \
--cc=gregg_99@mailcity.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