[OE-core] [oe-core][PATCH 1/1] qemumips64: no qemu-usermode for n32

Slater, Joseph joe.slater at windriver.com
Wed Oct 25 18:24:14 UTC 2017


I found that libn32-gobject-introspection would not compile without the remove, but I could check again.      Joe

-----Original Message-----
From: Andre McCurdy [mailto:armccurdy at gmail.com] 
Sent: Wednesday, October 25, 2017 10:19 AM
To: Alexander Kanavin
Cc: Slater, Joseph; OE Core mailing list
Subject: Re: [OE-core] [oe-core][PATCH 1/1] qemumips64: no qemu-usermode for n32

On Wed, Oct 25, 2017 at 4:14 AM, Alexander Kanavin <alexander.kanavin at linux.intel.com> wrote:
> On 10/25/2017 02:43 AM, Andre McCurdy wrote:
>>
>> On Tue, Oct 24, 2017 at 4:23 PM, Joe Slater <jslater at windriver.com> wrote:
>>>
>>> qemu-usermode is only available for mips64 and o32 code.
>>
>> Isn't that already handled by 
>> meta/conf/machine/include/mips/arch-mips.inc
>>
>>    # user mode qemu doesn't support mips64 n32: "Invalid ELF image 
>> for this architecture"
>>    MACHINE_FEATURES_BACKFILL_CONSIDERED_append = "
>> ${@bb.utils.contains('TUNE_FEATURES', 'n32', 'qemu-usermode', '', d)}"
>
> Yes, but this is really unreadable isn't it :) I don't see how anyone 
> could grasp that the above means "remove qemu-usermode from 
> MACHINE_FEATURES if
> n32 is in TUNE_FEATURES" (without diving into documentation).
>
> Any better way to express this would be appreciated.

Yes, BACKFILL_CONSIDERED always has been concept which baffles a lot of users - especially so since we quietly redefined it to mean not only "functionality which used to always be enabled but is now configurable" but now also "functionality which was not previously enabled but is now configurable and we want to enable by default and make it difficult for users to accidentally leave disabled".


More information about the Openembedded-core mailing list