From: "J . A . Magallon" <jamagallon@able.es>
To: Ken Moffat <ken@kenmoffat.uklinux.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Every Make option ends in error.
Date: Sat, 3 Feb 2001 01:11:51 +0100 [thread overview]
Message-ID: <20010203011151.G3014@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.21.0102022052090.31663-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.21.0102022052090.31663-100000@localhost.localdomain>; from ken@kenmoffat.uklinux.net on Fri, Feb 02, 2001 at 21:59:37 +0100
On 02.02 Ken Moffat wrote:
> Hi guys,
> I guess I'm doing something stupid, so please can somebody point it out
> and put me out of my misery ?
>
> Copied a plain 2.4.0 tree to a new directory, patched it to 2.4.1 without
> any errors. Then I realised it had all the object files from my last
> compile, so I thought "make mrproper" was called for. It did a little,
> then
Do a 'cp -a linux-2.4.0 linux-2.4.1', and symlinks (asm...) will not be
de-referenced.
Or even better, if you are going to patch, do a 'cp -rl', and your new
tree will not waste almost any space (hard-links all the files, so space
only is duplicated when patch changes some file - and if you remove the
old kernel tree, the space just goes to the new).
--
J.A. Magallon $> cd pub
mailto:jamagallon@able.es $> more beer
Linux werewolf 2.4.1-ac1 #2 SMP Fri Feb 2 00:19:04 CET 2001 i686
-
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/
next prev parent reply other threads:[~2001-02-03 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 20:59 Every Make option ends in error Ken Moffat
2001-02-02 21:14 ` Richard B. Johnson
2001-02-02 21:51 ` Ken Moffat
2001-02-02 21:53 ` Alan Cox
2001-02-03 0:11 ` J . A . Magallon [this message]
2001-02-04 0:35 ` Rusty Russell
[not found] <Pine.LNX.4.10.10102021608570.6971-100000@coffee.psychology.mcmaster.ca>
2001-02-02 21:21 ` Ken Moffat
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=20010203011151.G3014@werewolf.able.es \
--to=jamagallon@able.es \
--cc=ken@kenmoffat.uklinux.net \
--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