Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Linux kernel: host-libyaml dependency
Date: Thu, 30 Jan 2020 23:33:34 +0100	[thread overview]
Message-ID: <87lfposhfl.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAGm1_ktWWnNymXDhkKowu+0u2DSwqNA-3dW6hHy_omW_PXXdOg@mail.gmail.com> (Yegor Yefremov's message of "Wed, 29 Jan 2020 08:41:45 +0100")

>>>>> "Yegor" == Yegor Yefremov <yegorslists@googlemail.com> writes:

 > I had a build breakage during the 5.4.15 kernel compilation because of
 > the missing yaml library. The code in kernel is under scripts/dtc.

Hmm, what is the error exactly?

Is it this? From scripts/dtc/Makefile:

ifeq ($(shell pkg-config --exists yaml-0.1 2>/dev/null && echo yes),)
ifneq ($(CHECK_DTBS),)
$(error dtc needs libyaml for DT schema validation support. \
        Install the necessary libyaml development package.)

This seems to come from:

commit 4f0e3a57d6eb727c54249542c509e0b7aa122465
Author: Rob Herring <robh@kernel.org>
Date:   Thu Sep 6 13:26:07 2018 -0500

    kbuild: Add support for DT binding schema checks

    This adds the build infrastructure for checking DT binding schema
    documents and validating dts files using the binding schema.

    Check DT binding schema documents:
    make dt_binding_check

    Build dts files and check using DT binding schema:
    make dtbs_check

    Optionally, DT_SCHEMA_FILES can be passed in with a schema file(s) to
    use for validation. This makes it easier to find and fix errors
    generated by a specific schema.

    Currently, the validation targets are separate from a normal build to
    avoid a hard dependency on the external DT schema project and because
    there are lots of warnings generated.


But this shouldn't trigger unless you are running 'make dtbs_check',
which you presumably aren't?


 > Has anyone encountered such a problem? Should we add host-libyaml
 > unconditionally?

We should definately not do it unconditionally, as it seems to only be
needed for (a subset of the) systems using device-tree.

Can you be more specific about what config triggers this for you?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2020-01-30 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29  7:41 [Buildroot] Linux kernel: host-libyaml dependency Yegor Yefremov
2020-01-30 22:33 ` Peter Korsgaard [this message]
2020-01-31  9:33   ` Yegor Yefremov
2020-01-31 10:57     ` Peter Korsgaard

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=87lfposhfl.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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