public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Kristian Peters <kristian.peters@korseby.net>,
	linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>
Subject: Re: -ac series won't compile without fix
Date: Mon, 10 Jun 2002 16:14:21 -0400	[thread overview]
Message-ID: <3D05089D.6030604@blue-labs.org> (raw)
In-Reply-To: <20020605134945.7ad22093.kristian.peters@korseby.net> <30073.1023366073@redhat.com>

So in other words...

$ tar zxf linux.tar.bz2
$ patch -p1 < patch
$ cp /boot../.config .
$ make oldconfig
$ make dep clean
$ make -j3 bzImage
$ make dep
$ make -j3 bzImage

That about cover it?  Still doesn't work.  I'm using -ac2.

-d


David Woodhouse wrote:

>kristian.peters@korseby.net said:
>  
>
>>I'm unable to compile the -ac series correctly.  A "make mrproper"
>>does not help here.
>>    
>>
>
>  
>
>>make[1]: *** No rule to make target `/usr/src/linux-2.4.19-pre10-ac1/fs/inflate_fs/infblock.h', needed by `/usr/src/linux-2.4.19-pre10-ac1/fs/inflate_fs/infcodes.h'.  Stop.
>>    
>>
>
>This is one of many symptoms of the broken kbuild system in current 2.4 and
>2.5 kernels. You need to re-run 'make dep'.
>
>--
>dwmw2
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>  
>


  reply	other threads:[~2002-06-10 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 11:49 -ac series won't compile without fix Kristian Peters
2002-06-06 12:21 ` David Woodhouse
2002-06-10 20:14   ` David Ford [this message]
2002-06-10 20:28     ` Kristian Peters

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=3D05089D.6030604@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=alan@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=kristian.peters@korseby.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