From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:47652)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.friesen@genband.com>) id 1R9hbs-0003P5-18
	for qemu-devel@nongnu.org; Fri, 30 Sep 2011 14:14:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <chris.friesen@genband.com>) id 1R9hbq-0003MU-M6
	for qemu-devel@nongnu.org; Fri, 30 Sep 2011 14:14:55 -0400
Received: from exprod7og118.obsmtp.com ([64.18.2.8]:37236)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <chris.friesen@genband.com>) id 1R9hbq-0003M8-EC
	for qemu-devel@nongnu.org; Fri, 30 Sep 2011 14:14:54 -0400
Message-ID: <4E860703.5000906@genband.com>
Date: Fri, 30 Sep 2011 12:14:27 -0600
From: Chris Friesen <chris.friesen@genband.com>
MIME-Version: 1.0
References: <4E85F741.2050100@genband.com> <4E8601C8.7030109@twiddle.net>
In-Reply-To: <4E8601C8.7030109@twiddle.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [BUG] need to export variables in config.mak
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Richard Henderson <rth@twiddle.net>
Cc: Jan Kiszka <jan.kiszka@web.de>, qemu-devel@nongnu.org, kvm@vger.kernel.org, Avi Kivity <avi@redhat.com>

On 09/30/2011 11:52 AM, Richard Henderson wrote:
> On 09/30/2011 10:07 AM, Chris Friesen wrote:
>> We've been playing a bit with kvm-kmod-3.0b.  We use a cross compile
>> environment, and one of my coworkers noticed that the variables in
>> config.mak weren't actually exported and so didn't actually have any
>> effect.
>
> Please elaborate on "no effect", and what actual problems you are
> experiencing.  I do cross-compilation builds all the time and have
> no such problems.

The behaviour I see is that I configure with --cross-prefix=<prefix> 
then the appropriate prefix gets set in config.mak.  However, when 
running "make" the prefix doesn't actually get used.

If building for the same target as the host machine this isn't 
immediately obvious because it uses the host compiler.  However, if you 
run "make V=1" it will show which compiler is being used.

Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com