All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH] Fixes for build/install system
Date: Wed, 1 Apr 2009 08:44:39 +0100	[thread overview]
Message-ID: <200904010944.39425.Christoph.Egger@amd.com> (raw)
In-Reply-To: <18898.16577.474687.221544@mariner.uk.xensource.com>

On Tuesday 31 March 2009 18:11:45 Ian Jackson wrote:
> Christoph Egger writes ("[PATCH] Fixes for build/install system"):
> > Attached patches get rid of hardcoded install path,
> > fixes wrong install paths and replaces mkdir -p with $(INSTALL_DIR).
> > All in all, a command like PREFIX="/usr/local" gmake dist
> > now installs everything into dist/install/usr/local
> > instead of dist/install/usr
>
> This is all very nice but
>
> >  install-doc: $(DOCS)
> > -	mkdir -p "$(DESTDIR)$(docdir)"
> > +	$(INSTALL_DIR) "$(DESTDIR)$(docdir)"
> >  	$(INSTALL) -m 644 qemu-doc.html  qemu-tech.html "$(DESTDIR)$(docdir)"
>
> these are parts of the Makefile which come from upstream qemu.
> I definitely don't want to modify those parts.  Everything which is
> done in the makefiles in qemu-xen-unstable is aimed at avoiding large
> textual changes which make merging difficult.  We don't want changes
> in our versions of the upstream makefiles which are not absolutely
> necessary to make things work.
>
> It's not clear to me by inspection whether I can safely apply the
> other parts of your qemu patch on their own.  Can you confirm ?

Yes, I can confirm. It is just less consistent throughout the whole
xen build/install system.

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Jochen Polster, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2009-04-01  7:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 12:22 [PATCH] Fixes for build/install system Christoph Egger
2009-03-31 16:11 ` Ian Jackson
2009-04-01  7:44   ` Christoph Egger [this message]
     [not found] ` <200904221037.00833.Christoph.Egger@amd.com>
     [not found]   ` <18927.13912.58144.792099@mariner.uk.xensource.com>
2009-04-22 15:46     ` [PATCH] ioemu: " Christoph Egger
2009-04-23 15:43       ` Ian Jackson
2009-04-23 15:54         ` Christoph Egger
2009-04-23 17:19           ` Ian Jackson
2009-04-24  6:34             ` Christoph Egger
2009-04-29 15:30               ` Ian Jackson
2009-05-04  9:42                 ` Christoph Egger
2009-05-05 14:00                   ` Ian Jackson
2009-05-05 14:15                     ` Christoph Egger
2009-05-05 14:28                       ` Ian Jackson
2009-05-05 15:25                         ` Christoph Egger
2009-05-05 17:22                           ` Ian Jackson
2009-05-08  9:29                             ` Christoph Egger
2009-05-08 16:13                               ` Ian Jackson

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=200904010944.39425.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --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.