All of lore.kernel.org
 help / color / mirror / Atom feed
From: tdc <tdc@phreaker.net>
To: xen-devel@lists.xensource.com
Subject: Bug in 2.0.6 "buildconfigs" ?
Date: Mon, 23 May 2005 15:25:58 +0200	[thread overview]
Message-ID: <4291D9E6.50109@phreaker.net> (raw)

I think there is a bug in mk.linux-2.6-* scripts which leads to always
using xenX-defconfigs and ignoring configs in dist/install/boot.

On line 34 in mk.linux-2.6-* you check for file:
$(DESTDIR)/boot/config-$(LINUX_VER)$$CONFIG_VERSION
this evals to filename "config-2.6.11.10$(XENGUEST)", which is obviously
wrong. Makefiles in toplevel kernel trees does have the same error in it
(these are set on line 30 in mk.linux-2.6.*)
Makefile (for xen0) then starts with:
---
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 11
EXTRAVERSION = .10$(XENGUEST)
XENGUEST = -xen0
NAME=Woozy Beaver
---

Downloaded today at 13:08 from
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-2.0.6-src.tgz

Dave

             reply	other threads:[~2005-05-23 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 13:25 tdc [this message]
2005-05-23 23:59 ` Bug in 2.0.6 "buildconfigs" ? Christian Limpach
  -- strict thread matches above, loose matches on Subject: below --
2005-06-28 14:19 Bill Burns

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=4291D9E6.50109@phreaker.net \
    --to=tdc@phreaker.net \
    --cc=xen-devel@lists.xensource.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 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.