Re: [Xen-devel] [PATCH RFC 12/20] acpi/hvmloader: Link ACPI object files directly

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 06.06.16 at 17:31, <andrew.cooper3@xxxxxxxxxx> wrote:
> On 06/06/16 15:49, Boris Ostrovsky wrote:
>> On 06/06/2016 10:29 AM, Jan Beulich wrote:
>>>> How would this help with avoiding building the intermediate files
>>>> from multiple paces (libxc and hvmloader specifically --- that was
>>>> the reason for .NOTPARALLEL). 
>>> If you symlink the source files into three different subdirectories,
>>> building in those three subdirectories will become independent. (Or,
>>> just like libelf, build the hypervisor part in the actual directory, and
>>> symlink only the libxc and hvmloader uses.)
>> I see. I didn't want to generate intermediate files multiple times but
>> yes, it's better than dealing with make synchronization issues.
> 
> It is exceedingly unlikely that Xen, the toolstack, and hvmloader will
> have libacpi compiled with the same compiler settings.
> 
> Sharing intermediate files is not safe to do in this context.

But you realize we don't talk about compiler settings here? The
intermediate .c files are to represent compiled .asl ones, and
the .asl -> .c conversion is much more likely to happen in mostly
similar fashion. But I can foresee customization, which would end
up being different between the consumer environments.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel