linux-kernel - Re: [PATCH] scripts/dtc: Call pkg-config POSIXly correct

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL_JsqJ=OBDgemXxa6vH_t-SVr2JKUGdQ2+VoHTZSodyUiPROQ@mail.gmail.com>
Date:   Mon, 31 Jan 2022 08:43:17 -0600
From:   Rob Herring <robh+dt@...nel.org>
To:     Thomas Bracht Laumann Jespersen <t@...mann.xyz>
Cc:     Frank Rowand <frowand.list@...il.com>,
        Masahiro Yamada <masahiroy@...nel.org>,
        devicetree@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] scripts/dtc: Call pkg-config POSIXly correct

On Mon, Jan 31, 2022 at 5:20 AM Thomas Bracht Laumann Jespersen
<t@...mann.xyz> wrote:
>
> Running with POSIXLY_CORRECT=1 in the environment the scripts/dtc build
> fails, because pkg-config doesn't output anything when the flags come
> after the arguments.
>
> Fixes: f8d8b46cd20e ("scripts/dtc: use pkg-config to include <yaml.h> in non-standard path")

It's actually 067c650c456e ("dtc: Use pkg-config to locate libyaml")
that you are fixing.

I can fix when applying.

Rob