Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Peter Seiderer <ps.report@gmx.net>,
	Julien Corjon <corjon.j@ecagroup.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/qt5/q5doc: fix dependency
Date: Mon, 15 Aug 2022 11:35:32 +0200	[thread overview]
Message-ID: <20220815113532.6b1c844a@windsurf> (raw)
In-Reply-To: <20220810104450.3424068-1-fontaine.fabrice@gmail.com>

On Wed, 10 Aug 2022 12:44:50 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Commit fa917d0ca96baf4ef877a80e57d438bfbb8cdf2d forgot to add
> BR2_PACKAGE_QT5_JSCORE_AVAILABLE dependency:
> 
> WARNING: unmet direct dependencies detected for BR2_PACKAGE_QT5DECLARATIVE
>   Depends on [n]: BR2_PACKAGE_QT5 [=y] && BR2_PACKAGE_QT5_JSCORE_AVAILABLE [=n]
>   Selected by [y]:
>   - BR2_PACKAGE_QT5DOC [=y] && BR2_PACKAGE_QT5 [=y]
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/qt5/qt5doc/Config.in | 1 +
>  1 file changed, 1 insertion(+)

Applied to master, thanks. Sadly, it's only after pushing that I
noticed the typo in the commit title (q5doc -> qt5doc). Oh well :-/

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-08-15  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 10:44 [Buildroot] [PATCH 1/1] package/qt5/q5doc: fix dependency Fabrice Fontaine
2022-08-15  9:35 ` Thomas Petazzoni via buildroot [this message]

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=20220815113532.6b1c844a@windsurf \
    --to=buildroot@buildroot.org \
    --cc=corjon.j@ecagroup.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=ps.report@gmx.net \
    --cc=thomas.petazzoni@bootlin.com \
    /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