From: Peter Osterlund <petero2@telia.com>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: KBuild 2.5 Impressions
Date: 02 Jun 2002 13:53:33 +0200 [thread overview]
Message-ID: <m2bsathp6q.fsf@ppro.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0206020534461.29405-100000@hawkeye.luckynet.adm>
Thunder from the hill <thunder@ngforever.de> writes:
> On 2 Jun 2002, Peter Osterlund wrote:
> > 3. You have to remember the "-f Makefile-2.5" arguments to make,
> > otherwise it will use the old makefile system. This seems to mess
> > things up so that subsequent make commands fail.
> > I tried to "mv Makefile-2.5 Makefile" to overcome this problem, but
> > it doesn't work because the original Makefile appears to be needed
> > for extracting kernel version information.
>
> There was no intention to reinvent the wheel. The only _replacing_
> Makefile is a _merged_ version of them. Then you'll also have to find any
> Makefile-2.5s and revert them to Makefiles. This will take a moment, and
> is not yet intented.
Yes, I realize this problem will go away automatically when support
for the old makefile system is removed. I just wanted to present my
complete list of problems with kbuild 2.5. Except for those three
issues, I don't see any advantages with the old makefile system.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2002-06-02 11:53 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 9:45 KBuild 2.5 Impressions Daniel Phillips
2002-05-30 12:50 ` Martin Dalecki
2002-05-30 14:08 ` Kenneth Johansson
2002-05-30 13:28 ` Paul P Komkoff Jr
2002-05-30 21:55 ` Ion Badulescu
2002-05-30 22:29 ` Thunder from the hill
2002-05-30 23:19 ` Daniel Phillips
2002-05-31 0:09 ` David Lang
2002-05-31 0:29 ` Daniel Phillips
2002-05-31 0:32 ` Larry McVoy
2002-06-03 7:21 ` Rusty Russell
2002-05-31 0:13 ` Kenneth Johansson
2002-05-31 0:47 ` Daniel Phillips
2002-05-31 1:20 ` Skip Ford
2002-05-31 1:24 ` Daniel Phillips
2002-05-31 13:48 ` Tomas Szepe
2002-05-31 14:28 ` Nicolas Pitre
2002-05-31 15:21 ` Thunder from the hill
[not found] ` <Pine.LNX.4.44.0205302129120.29405-100000@hawkeye.luckynet.adm>
2002-05-31 4:01 ` Skip Ford
2002-05-31 4:46 ` KBuild 2.5 Migration Daniel Phillips
2002-05-31 5:12 ` Skip Ford
2002-05-31 0:48 ` KBuild 2.5 Impressions Nicolas Pitre
2002-05-31 3:29 ` Hua Zhong
2002-05-31 3:39 ` Daniel Phillips
2002-05-31 3:55 ` Thunder from the hill
2002-06-02 4:03 ` Ion Badulescu
2002-06-02 6:51 ` Daniel Phillips
2002-06-02 7:58 ` Thunder from the hill
2002-06-02 14:03 ` Sam Ravnborg
2002-06-02 14:38 ` Daniel Phillips
2002-06-02 14:56 ` Sam Ravnborg
2002-06-02 15:05 ` Thunder from the hill
2002-06-02 15:16 ` Daniel Phillips
2002-06-02 18:26 ` Sam Ravnborg
2002-06-02 18:39 ` Thunder from the hill
2002-06-02 18:57 ` Ion Badulescu
2002-06-02 19:15 ` Thunder from the hill
2002-06-03 2:04 ` Kai Germaschewski
2002-06-02 15:47 ` Thunder from the hill
2002-06-02 11:21 ` Peter Osterlund
2002-06-02 11:37 ` Thunder from the hill
2002-06-02 11:53 ` Peter Osterlund [this message]
2002-06-02 12:03 ` Thunder from the hill
2002-06-02 12:09 ` Thunder from the hill
2002-06-02 12:51 ` Peter Osterlund
2002-06-02 14:00 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 2:49 Dan Kegel
2002-06-03 3:28 ` Linus Torvalds
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=m2bsathp6q.fsf@ppro.localdomain \
--to=petero2@telia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=thunder@ngforever.de \
/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.