public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <aliguori-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Enhance libkvm Makefile
Date: Fri, 03 Nov 2006 08:08:41 +0200	[thread overview]
Message-ID: <454ADCE9.7000505@qumranet.com> (raw)
In-Reply-To: <454A9578.1080100-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>

Anthony Liguori wrote:
> The attached patch allows for DESTDIR/PREFIX to be used with the 
> libkvm Makefile as one may expect the should be used.  Also, it lets 
> KERNELDIR be specified.
>

Thanks, this is useful.


> Regards,
>
> Anthony Liguori
>
> Signed-off-by: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
> ------------------------------------------------------------------------
>
> diff -r ca0347086805 Makefile
> --- a/Makefile	Thu Nov 02 18:59:50 2006 -0600
> +++ b/Makefile	Thu Nov 02 19:00:05 2006 -0600
> @@ -1,12 +1,11 @@
>  
> -KERNELDIR = ../kernel
> +KERNELDIR ?= ../kernel
> +PREFIX ?= /usr/local
>   

I dislike '?=' since it makes a simple 'make' depend on environment 
variables, so a build can have different results depending on which 
xterm you happen to be in.

A regular assignment can be overridden on the make command line, but 
that's somewhat tedious.  I think a simple ./configure (NOT the 
autotools thing) is best.



>  
>  CFLAGS = -I $(KERNELDIR)/include $(autodepend-flags) -g
>  CXXFLAGS = $(autodepend-flags) 
>  
>  autodepend-flags = -MMD -MF $(dir $*).$(notdir $*).d
> -
> -DESTDIR = /usr/local
>  
>   

Ditto.  DESTDIR should be initialized.

>  ifeq ($(shell uname -m), x86_64)
>  LIBDIR = /lib64
> @@ -25,10 +24,10 @@ flatfiles: test/simple.flat test/stringi
>  	test/irq.flat test/sieve.flat test/bootstrap
>  
>  install:
> -	install -D kvmctl.h $(DESTDIR)/include/kvmctl.h
> +	install -D kvmctl.h $(DESTDIR)$(PREFIX)/include/kvmctl.h
>  	install -D $(KERNELDIR)/include/linux/kvm.h \
> -		$(DESTDIR)/include/linux/kvm.h
> -	install -D libkvm.a $(DESTDIR)/$(LIBDIR)/libkvm.a
> +		$(DESTDIR)$(PREFIX)/include/linux/kvm.h
> +	install -D libkvm.a $(DESTDIR)$(PREFIX)/$(LIBDIR)/libkvm.a
>  
>  %.flat: %.o
>  	gcc -nostdlib -o $@ -Wl,-T,flat.lds $^
>   


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  parent reply	other threads:[~2006-11-03  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03  1:03 [PATCH] Enhance libkvm Makefile Anthony Liguori
     [not found] ` <454A9578.1080100-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org>
2006-11-03  6:08   ` Avi Kivity [this message]
     [not found]     ` <454ADCE9.7000505-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-03  6:41       ` Anthony Liguori

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=454ADCE9.7000505@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=aliguori-NZpS4cJIG2HvQtjrzfazuQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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