All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Andersen <rasmus@jaquet.dk>
To: Keith Owens <kaos@ocs.com.au>
Cc: Anders Karlsson <anders.karlsson@meansolutions.com>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-ac10 compile errors
Date: Tue, 23 Jan 2001 13:29:07 +0100	[thread overview]
Message-ID: <20010123132907.C20488@jaquet.dk> (raw)
In-Reply-To: <20010123121611.A3723@alien.ssd.hursley.ibm.com> <23997.980252378@ocs3.ocs-net>
In-Reply-To: <23997.980252378@ocs3.ocs-net>; from kaos@ocs.com.au on Tue, Jan 23, 2001 at 11:19:38PM +1100

On Tue, Jan 23, 2001 at 11:19:38PM +1100, Keith Owens wrote:
> On Tue, 23 Jan 2001 12:16:11 +0000, 
> Anders Karlsson <anders.karlsson@meansolutions.com> wrote:
> >Even if it is a pristine kernel tree? What function does the 'make
> >mrproper' fill on an unused kernel tree?
> 
> Depends on how you removed the old tree.  If you did 'rm -rf *' then
> some dot files are left around.  make mrproper removes dot files, it
> may or may not be the fix.

I think that Alan left some autogenerated files in ac10 which
you need make mrproper to delete properly.

Regards,
  Rasmus
-
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/

  reply	other threads:[~2001-01-23 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-23 10:48 2.4.0-ac10 compile errors Anders Karlsson
2001-01-23 11:43 ` Keith Owens
2001-01-23 12:16   ` Anders Karlsson
2001-01-23 12:19     ` Keith Owens
2001-01-23 12:29       ` Rasmus Andersen [this message]
2001-01-23 12:52         ` Anders Karlsson
     [not found]       ` <Your message of "Tue, 23 Jan 2001 12:16:11 -0000." <20010123121611.A3723@alien.ssd.hursley.ibm.com>
2001-01-23 12:29         ` Anton Altaparmakov

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=20010123132907.C20488@jaquet.dk \
    --to=rasmus@jaquet.dk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anders.karlsson@meansolutions.com \
    --cc=kaos@ocs.com.au \
    --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 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.