public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xuan Baldauf <xuan--lkml@baldauf.org>
To: root@chaos.analogic.com
Cc: Keith Owens <kaos@ocs.com.au>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Version 2.4.1 cannot be built.
Date: Wed, 31 Jan 2001 00:01:26 +0100	[thread overview]
Message-ID: <3A7747C6.5DBEA6EB@baldauf.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1010130175517.3672A-100000@chaos.analogic.com>



"Richard B. Johnson" wrote:

> On Wed, 31 Jan 2001, Keith Owens wrote:
>
> > On Tue, 30 Jan 2001 16:45:16 -0500 (EST),
> > "Richard B. Johnson" <root@chaos.analogic.com> wrote:
> > >The subject says it all. `make dep` is now broken.
> > >make[4]: Entering directory `/usr/src/linux-2.4.1/drivers/acpi'
> > >Makefile:29: *** target pattern contains no `%'.  Stop.
> >
> > Which version of make are you running?
> >
>         3.74
>
> y'a mean even make isn't make anymore?
> Temporary 'fix' was `make -i` for the dependencies. All files I
> need built okay.

I experienced similar problems with make 3.76.1. After upgrading to 3.79.1,
the problems were gone.

>
>
> Cheers,
> Dick Johnson
>
> Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
>
> "Memory is like gasoline. You use it up when you are running. Of
> course you get it all back when you reboot..."; Actual explanation
> obtained from the Micro$oft help desk.
>
> -
> 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/

-
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-30 23:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30 21:45 Version 2.4.1 cannot be built Richard B. Johnson
2001-01-30 22:13 ` Rik van Riel
2001-01-30 23:42   ` Reiserfs problem was: " Brett G. Person
2001-01-31  0:14     ` Chris Mason
2001-01-31 13:50   ` Richard B. Johnson
2001-01-30  3:15     ` Michael B. Trausch
2001-01-31 14:27       ` Richard B. Johnson
2001-01-31 13:55     ` Rik van Riel
2001-01-31 14:24       ` Richard B. Johnson
2001-01-31 14:35         ` Rik van Riel
2001-01-31 14:42           ` Richard B. Johnson
2001-01-31 14:48             ` David Woodhouse
2001-01-31 14:51               ` Rik van Riel
2001-01-31 14:48             ` Rik van Riel
2001-01-31 14:53             ` Mike Dresser
2001-01-31 15:01             ` Doug McNaught
2001-02-01 14:14             ` Matt Kemner
2001-01-31 15:03         ` James Sutherland
2001-02-02 22:22         ` Mo McKinlay
2001-01-30 22:36 ` Keith Owens
2001-01-30 22:57   ` Richard B. Johnson
2001-01-30 23:01     ` Xuan Baldauf [this message]
2001-01-30 23:04     ` Keith Owens
2001-01-30 23:09       ` Richard B. Johnson
2001-01-30 23:29         ` Keith Owens
2001-01-30 23:07     ` Richard B. Johnson
2001-01-31  6:14       ` Peter Samuelson
2001-01-31 18:37 ` mirabilos
  -- strict thread matches above, loose matches on Subject: below --
2001-01-31 14:49 anders.karlsson
     [not found] <20010131145059.D10769@dev.sportingbet.com>
2001-01-31 14:58 ` Richard B. Johnson

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=3A7747C6.5DBEA6EB@baldauf.org \
    --to=xuan--lkml@baldauf.org \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox