All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anatol Belski" <anbelski@linux.microsoft.com>
To: Yi Zhao <yi.zhao@windriver.com>, Joe MacDonald <joe@deserted.net>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-selinux][dunfell][gatesgarth][master][PATCH] libselinux-python: Fix build error due to missing target config
Date: Wed, 10 Mar 2021 12:14:45 +0100	[thread overview]
Message-ID: <04d6f1cc-79d9-c166-57c0-ab9bcb76a2b7@linux.microsoft.com> (raw)
In-Reply-To: <98f77c6a-8d89-fef4-0e5a-67ad67c28875@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 3054 bytes --]

Hi,

On 3/10/2021 6:30 AM, Yi Zhao wrote:
>
> On 3/9/21 11:32 PM, Joe MacDonald wrote:
>> [Re: [yocto] [meta-selinux][dunfell][gatesgarth][master][PATCH] 
>> libselinux-python: Fix build error due to missing target config] On 
>> 21.03.09 (Tue 14:53) Anatol Belski wrote:
>>
>>> Hi Joe,
>>>
>>> thanks for the quick check. The patch applies fine to dunfell and
>>> gatesgarth, master has the changed recipe version in the bb name. I was
>>> about to rebase to master but pulling shows already did it. I was 
>>> too slow
>>> :) thanks for the quick fix.
>> No problem!  I assumed you were working on a just-slightly-out-of-date
>> master branch and my work tree already had your patch half applied when
>> the 'git am' failed, so I just finished that part up.
>
>
> Hi Joe,
>
>
> This patch doesn't need to be merged into master because I have fixed 
> it in commit fb15056ff44318d7886fd0f68e2f6dba716e9be4.

either way, a backport to dunfell and gatesgarth would be great to have 
then.

Thanks!

Anatol


> //Yi
>
>>
>> I'll get to the other branches in a bit.
>>
>> -Joe.
>>
>>> Regards
>>>
>>> Anatol
>>>
>>> On 3/9/2021 2:00 PM, Joe MacDonald wrote:
>>>> Hi Anatol,
>>>>
>>>> I will confirm this against the other branches (dunfell and 
>>>> gatesgarth)
>>>> but your patch doesn't appear to be against the current master 
>>>> branch (and
>>>> it's unlikely one patch will apply to all branches).  Can you send out
>>>> specific patches against the head of tree for each branch you care 
>>>> about,
>>>> please?  Then I can get them merged for you.
>>>>
>>>> Thanks,
>>>> -Joe.
>>>>
>>>> [[yocto] [meta-selinux][dunfell][gatesgarth][master][PATCH] 
>>>> libselinux-python: Fix build error due to missing target config] On 
>>>> 21.03.09 (Tue 11:55) Anatol Belski wrote:
>>>>
>>>>> This fixes the error below:
>>>>>
>>>>> gcc: error: unrecognized command line option
>>>>> ‘-fmacro-prefix-map=/path/to/build/libselinux-python/3.0-r0=/usr/src/debug/libselinux-python/3.0-r0’ 
>>>>>
>>>>>
>>>>> Without inheriting the config, supposedly a wrong compiler is used.
>>>>>
>>>>> Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>
>>>>> ---
>>>>>    recipes-security/selinux/libselinux-python_3.0.bb | 2 ++
>>>>>    1 file changed, 2 insertions(+)
>>>>>
>>>>> diff --git a/recipes-security/selinux/libselinux-python_3.0.bb 
>>>>> b/recipes-security/selinux/libselinux-python_3.0.bb
>>>>> index 2b5438d..3c03df1 100644
>>>>> --- a/recipes-security/selinux/libselinux-python_3.0.bb
>>>>> +++ b/recipes-security/selinux/libselinux-python_3.0.bb
>>>>> @@ -4,6 +4,8 @@ SRC_URI = 
>>>>> "https://github.com/SELinuxProject/selinux/releases/download/${SELINUX 
>>>>>
>>>>>    require ${BPN}.inc
>>>>> +inherit python3targetconfig
>>>>> +
>>>>>    LIC_FILES_CHKSUM = 
>>>>> "file://LICENSE;md5=84b4d2c6ef954a2d4081e775a270d0d0"
>>>>>    SRC_URI[md5sum] = "b387a66f087b6d97713570e85ec89d89"
>>>>> -- 
>>>>> 2.17.1
>>>>>
>>>>>
>>>>>
>
> 
>

[-- Attachment #2: Type: text/html, Size: 5777 bytes --]

      reply	other threads:[~2021-03-10 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 11:55 [meta-selinux][dunfell][gatesgarth][master][PATCH] libselinux-python: Fix build error due to missing target config Anatol Belski
2021-03-09 13:00 ` [yocto] " Joe MacDonald
2021-03-09 13:53   ` Anatol Belski
2021-03-09 15:32     ` Joe MacDonald
2021-03-10  5:30       ` Yi Zhao
2021-03-10 11:14         ` Anatol Belski [this message]

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=04d6f1cc-79d9-c166-57c0-ab9bcb76a2b7@linux.microsoft.com \
    --to=anbelski@linux.microsoft.com \
    --cc=joe@deserted.net \
    --cc=yi.zhao@windriver.com \
    --cc=yocto@yoctoproject.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.