Re: [PATCH] [RESEND] Add cross compile to top level configuration file

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Jerone Young wrote:
>   
>>>  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?
>>     
>
> I can create two but it will make things very complicated. This only
> will effect the qemu and user directory, but not the kernel directory.
> Currently kernel directory is used for headers by these two. 
>
> If a user wants to change this they can run the configure script in user
> directory manually. 
>
> Really I can just change it to just the option is --cc and remove the
> qemu part.  That actually makes more since.
>
> Otherwise you end up with something more complicated like having to
> specify which one needs the cross compiler and not, which need this
> specific gcc, just bad. Really you should be compiling both with the
> same gcc anyway. If you want to do something different then you really
> should go into both directories and run configure stand alone. 
>   

So long as the kernel isn't affected I don't mind a common cc for user/
and qemu/.

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


-------------------------------------------------------------------------
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/