linux-kernel - Re: [PATCH] dtc: also check <yaml.h> for libyaml

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAK7LNASj5nABYN0ukE_V3aK_ys7zuAibn4bzy8x5zGHM59gF1g@mail.gmail.com>
Date:   Wed, 10 Jun 2020 10:31:19 +0900
From:   Masahiro Yamada <masahiroy@...nel.org>
To:     Jiping Ma <Jiping.Ma2@...driver.com>
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 Wed, Jun 10, 2020 at 10:12 AM Jiping Ma <Jiping.Ma2@...driver.com> wrote:
>
>
>
> 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.


Then, I have no idea,
but this is not a problem in the kernel build.



-- 
Best Regards
Masahiro Yamada