From: Steven Smith <sos22@cam.ac.uk>
To: Richard Adams <pa3gcu@zeelandnet.nl>
Cc: Staci <spiritlover666@yahoo.com>, linux-newbie@vger.kernel.org
Subject: Re: register_exec_domain
Date: Sat, 27 Apr 2002 10:31:06 +0100 [thread overview]
Message-ID: <20020427093106.GA1303@cam.ac.uk> (raw)
In-Reply-To: <0204270705050A.04696@unix.pa3gcu>
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
> > > Did you do a 'make mrproper' before anything else?
> > Dunno if you know, but mrproper can corrupt things.
> In any case you have to
> use make mrproper when you install a new kernel source otherwise things like
> symlinks to /usr/include are not created.
As far as I can see from reading the makefiles, and from looking at
the output when it's actually run, make mrproper does not create any
symlinks. Old libcs (pre version 6) needed symlinks from /usr/include
into the kernel include files, but that's obsolete with glibc, and
tends to cause more problems than it solves.
> > i always use make clean. :)
> That will not help when installing a new kernel source.
> If you look into the kernel source top dir Makefile you will see that "clean"
> only removes an amount of unwanted configureation *.h files, mrproper removes
> logfiles, files preceeded with a . (as in) .config, removes old symlinks and
> recreates them + much much more.
Some would argue that removing a config file is the limiting case of
corrupting it :). Plus, new tarballs of kernel sources are supposed to
be clean and mrproper to begin with.
Anyway, if you want a really clean source tree, make distclean is more
thorough, as it gets rid of patch(1) related detritus as well, which
mrproper has a habit of leaving behind.
Steven Smith,
sos22@cam.ac.uk.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-04-27 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020422094901.57fc79e6.jeremy@kerneltrap.org>
2002-04-25 11:48 ` register_exec_domain G Anna
2002-04-26 11:52 ` register_exec_domain Jeremy Andrews
2002-04-27 1:02 ` register_exec_domain Staci
2002-04-27 7:05 ` register_exec_domain Richard Adams
2002-04-27 9:31 ` Steven Smith [this message]
2003-03-12 7:12 ` register_exec_domain pshook
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=20020427093106.GA1303@cam.ac.uk \
--to=sos22@cam.ac.uk \
--cc=linux-newbie@vger.kernel.org \
--cc=pa3gcu@zeelandnet.nl \
--cc=spiritlover666@yahoo.com \
/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.