[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c5b1422-5b8a-03fe-57ea-567767ed75e2@windriver.com>
Date: Wed, 10 Jun 2020 09:12:12 +0800
From: Jiping Ma <Jiping.Ma2@...driver.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: Rob Herring <robh@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
DTML <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dtc: also check <yaml.h> for libyaml
On 06/10/2020 08:28 AM, Masahiro Yamada wrote:
> On Tue, Jun 9, 2020 at 12:08 PM Jiping Ma <Jiping.Ma2@...driver.com> wrote:
>>
>>
>> On 06/09/2020 10:52 AM, Masahiro Yamada wrote:
>>> On Tue, Jun 9, 2020 at 10:01 AM Jiping Ma <Jiping.Ma2@...driver.com> wrote:
>>>>
>>>> On 06/09/2020 03:09 AM, Rob Herring wrote:
>>>>> On Mon, Jun 8, 2020 at 2:42 AM Jiping Ma <jiping.ma2@...driver.com> wrote:
>>>>>> yamltree.c includes <yaml.h>, If /usr/include/yaml.h does not exist,
>>>>>> it fails to build.
>>>>> Does this patch fix your issue?:
>>>>>
>>>>> https://lore.kernel.org/linux-devicetree/20200505100319.741454-1-masahiroy@kernel.org/
>>>> No, it did not fix the issue.
>>>>
>>>> $ pkg-config --cflags yaml-0.1
>>>>
>>>> $ pkg-config yaml-0.1 --libs
>>>> -L/buildarea/jma1/wr-19-0518/19.45/sysroots/aarch64-wrs-linux/usr/lib64
>>>> -lyaml
>> This issue happened in Yocto, After completing the SDK build and
>> installing it, use a new shell to source the environment and try to
>> build the helper scripts.
>> export
>> SDKTARGETSYSROOT=/buildarea/jma1/wr-19-0518/19.45/sysroots/aarch64-wrs-linux
>> export
>> PKG_CONFIG_PATH=$SDKTARGETSYSROOT/usr/lib64/pkgconfig:$SDKTARGETSYSROOT/usr/share/pkgconfig
>>>
>
> Probably, this commit:
>
> https://github.com/yaml/libyaml/commit/3c80be99fb18f3ee18af37221a3b0c4760e8df06
>
>
> Use newer libyaml, and that's fine.
This commit already was included in our code.
>
>
Powered by blists - more mailing lists