Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14881] New: Watchdogd Package missing INSTALL_STAGING
Date: Tue, 28 Jun 2022 11:28:57 +0000	[thread overview]
Message-ID: <bug-14881-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=14881

            Bug ID: 14881
           Summary: Watchdogd Package missing INSTALL_STAGING
           Product: buildroot
           Version: 2022.02.3
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: edrose@outramresearch.co.uk
                CC: buildroot@uclibc.org
  Target Milestone: ---

The watchdogd package in Buildroot is missing the `INSTALL_STAGING = YES`
option in it's makefile. The package provides a library called `libwdog.so`,
which is linked against when process supervision is used. Without installing in
the staging directory, programs that link against libwdog cannot find the
pkgconfig file when configuring and fail to build.

Adding `INSTALL_STAGING = YES` to watchdogd.mk fixes the build for programs
that use libwdog.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-06-28 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 11:28 bugzilla [this message]
2022-07-02 13:56 ` [Buildroot] [Bug 14881] Watchdogd Package missing INSTALL_STAGING bugzilla

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=bug-14881-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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