From: Peter Samuelson <peter@cadcamlab.org>
To: "Richard B. Johnson" <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:14:40 -0600 [thread overview]
Message-ID: <20010131001440.B18746@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1010130175517.3672A-100000@chaos.analogic.com> <Pine.LNX.3.95.1010130180303.4483A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1010130180303.4483A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Tue, Jan 30, 2001 at 06:07:32PM -0500
[Richard B. Johnson]
> Bob Tracy found the problem: the second ':' really needs to be
> escaped even though newer versions of make allow what was written.
> -$(MODINCL)/%.ver: CFLAGS := -I./include $(CFLAGS)
> +$(MODINCL)/%.ver: CFLAGS \:= -I./include $(CFLAGS)
No, that's a workaround in that it subverts the purpose of the line.
(In which case, better to delete the line entirely.) The correct fix
is to upgrade to a version of 'make' that understands the syntax used
there. Yes, the FSF being the FSF, they keep adding features to their
software. And yes, some of us are using some of those features.
It could have been worse. Documentation/Changes lists version 3.77,
from July 1998. We (at least I) actually considered using features
from 3.78, but that was quickly shot down since 3.78 is too new -
September 1999.
Peter
-
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-01-31 6:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 21:45 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
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 [this message]
2001-01-31 18:37 ` mirabilos
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=20010131001440.B18746@cadcamlab.org \
--to=peter@cadcamlab.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
all inboxes | Powered by JetHome®