linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiping Ma <Jiping.Ma2@windriver.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	DTML <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dtc: also check <yaml.h> for libyaml
Date: Wed, 10 Jun 2020 09:12:12 +0800	[thread overview]
Message-ID: <6c5b1422-5b8a-03fe-57ea-567767ed75e2@windriver.com> (raw)
In-Reply-To: <CAK7LNAQkXiw9cV=Qt5VrpDGd5CPAPS-EBs0AeOhSJd5JbXtkZg@mail.gmail.com>



On 06/10/2020 08:28 AM, Masahiro Yamada wrote:
> On Tue, Jun 9, 2020 at 12:08 PM Jiping Ma <Jiping.Ma2@windriver.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@windriver.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@windriver.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.
>
>


  reply	other threads:[~2020-06-10  1:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08  8:41 [PATCH] dtc: also check <yaml.h> for libyaml Jiping Ma
2020-06-08 19:09 ` Rob Herring
2020-06-09  1:00   ` Jiping Ma
2020-06-09  2:43     ` Masahiro Yamada
2020-06-09  2:52     ` Masahiro Yamada
2020-06-09  3:07       ` Jiping Ma
2020-06-10  0:28         ` Masahiro Yamada
2020-06-10  1:12           ` Jiping Ma [this message]
2020-06-10  1:31             ` Masahiro Yamada

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=6c5b1422-5b8a-03fe-57ea-567767ed75e2@windriver.com \
    --to=jiping.ma2@windriver.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).