From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH] [RESEND] Add cross compile to top level configuration file
Date: Tue, 16 Oct 2007 11:59:44 +0200 [thread overview]
Message-ID: <47148B90.2020607@qumranet.com> (raw)
In-Reply-To: <1192504130.5811.49.camel@thinkpad>
Jerone Young wrote:
> This new patch removes gcc 3.x checks, as well as adds environment
> variables $CFLAGS & $LDFLAGS to include libs to qemu for cross compile.
> I was going to add this in another patch. But they should probably go in
> now. So an example for power is to include zlib so before running
> configure you do:
> export LDFLAGS="-L/home/public/zlib-ppc/lib"
> export CFLAGS="-I/home/public/zlib-ppc/include"
>
>
Let's not add dependencies on environment variables. Explicit --options
please.
> Signed-on-by: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
>
> diff -r ff2feafadcac configure
> --- a/configure Fri Oct 12 07:35:25 2007 -0500
> +++ b/configure Mon Oct 15 21:52:51 2007 -0500
> @@ -3,32 +3,29 @@ prefix=/usr/local
> prefix=/usr/local
> kerneldir=/lib/modules/$(uname -r)/build
> want_module=1
> -qemu_cc=$(ls /usr/bin/gcc3* /usr/bin/gcc-3* 2>/dev/null | tail -n1)
>
> +cc=gcc
> disable_gcc_check=
> +cross_prefix=
> +arch=`uname -m`
> +target_exec=
>
> usage() {
> cat <<-EOF
> Usage: $0 [options]
>
> Options include:
> -
> + --arch=ARCH architecture to compile for ($arch)
> + --cross-prefix=PREFIX prefix for cross compiler
> --prefix=PREFIX where to install things ($prefix)
> --with-patched-kernel don't use external module
> --kerneldir=DIR kernel build directory ($kerneldir)
> - --qemu-cc="$qemu_cc" compiler for qemu (needs gcc3.x) ($qemu_cc)
> + --qemu-cc=CC compiler for qemu (needs to be gcc 3.x)
> + Not valid if used with --cross-prefix
> --disable-gcc-check don't insist on gcc-3.x
> - - this will break running without kvm
> + CAUTION: using this option may break build
>
Looks like a step back in terms of the amount of information provided to
the user.
> while [[ "$1" = -* ]]; do
> opt="$1"; shift
> @@ -48,11 +45,17 @@ while [[ "$1" = -* ]]; do
> want_module=
> ;;
> --qemu-cc)
> - qemu_cc="$arg"
> + cc="$arg"
>
This forces everything to be compiled with $cc, not just qemu? Or is
the kernel/ dierctory not affected by this?
> +qemudir=`pwd`/qemu
>
Add quoting so we can pretend we're safe in the presence of whitespace
in $PWD.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-16 9:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 19:12 [PATCH] Add cross compile to top level configuration file Jerone Young
2007-10-15 20:13 ` Anthony Liguori
[not found] ` <4713C9D5.3070001-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-15 20:35 ` Jerone Young
2007-10-15 20:51 ` Anthony Liguori
[not found] ` <4713D2BD.9040202-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-16 2:30 ` Jerone Young
2007-10-16 3:08 ` [PATCH] [RESEND] " Jerone Young
2007-10-16 9:59 ` Avi Kivity [this message]
[not found] ` <47148B90.2020607-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 19:08 ` Jerone Young
2007-10-16 19:58 ` Avi Kivity
2007-10-16 10:30 ` Avi Kivity
2007-10-16 9:37 ` [PATCH] " Avi Kivity
2007-10-16 14:59 ` Anthony Liguori
[not found] ` <4714D1BA.6050504-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-10-16 19:51 ` Jerone Young
2007-10-16 20:03 ` 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=47148B90.2020607@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@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 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.