public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.7-ac3
Date: 30 Jul 2001 10:32:11 -0700	[thread overview]
Message-ID: <9k45mr$mr1$1@cesium.transmeta.com> (raw)
In-Reply-To: <E15RBSL-0003cB-00@the-village.bc.nu> <23546.996493814@ocs3.ocs-net>

Followup to:  <23546.996493814@ocs3.ocs-net>
By author:    Keith Owens <kaos@ocs.com.au>
In newsgroup: linux.dev.kernel
>
> On Mon, 30 Jul 2001 12:43:29 +0100 (BST), 
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >How about we do
> >spec:	.version 
> >then ?
> 
> Same problem, no rule to create .version.  This should work.
> 
> spec:
> 	[ -e .version ] || echo 1 > .version
> 	. scripts/mkspec >kernel.spec
> 

The way .version is currently created is in fact a huge problem... it
means that if you do "make" as a user and then "make install" as root,
it will have to rebuild several files and relink the kernel.  My
opinion is that .version should probably be created as a side effect
of linking vmlinux.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2001-07-30 18:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30  0:22 Linux 2.4.7-ac3 Alan Cox
2001-07-30  3:47 ` Keith Owens
2001-07-30 11:16   ` Alan Cox
2001-07-30 11:25     ` Keith Owens
2001-07-30 11:43       ` Alan Cox
2001-07-30 11:50         ` Keith Owens
2001-07-30 17:32           ` H. Peter Anvin [this message]
2001-07-31  1:23             ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2001-07-31  7:55 Robert Cawley
2001-07-31 23:59 ` David Flood
2001-08-01  8:52   ` bvermeul

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='9k45mr$mr1$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --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