Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: "Bernd Kuhls" <bernd.kuhls@t-online.de>,
	"Raphaël Mélotte" <raphael.melotte@mind.be>,
	"Peter Seiderer" <ps.report@gmx.net>,
	"Ezequiel Garcia" <ezequiel@vanguardiasur.com.ar>,
	buildroot@buildroot.org, "Romain Naour" <romain.naour@gmail.com>,
	"Julien Corjon" <corjon.j@ecagroup.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/harfbuzz: bump to version 3.1.1
Date: Sun, 14 Nov 2021 15:08:06 +0100	[thread overview]
Message-ID: <20211114150806.2e39e94c@windsurf> (raw)
In-Reply-To: <20211108183519.2561478-2-giulio.benetti@benettiengineering.com>

Hello Giulio,

On Mon,  8 Nov 2021 19:35:19 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> Bump to version 3.1.1 by:
> - requiring BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 instead of _4_8 in this
> package taking care of reverse dependencies, since now harfbuzz requires
> gcc 4.9 to be built successfully.
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>

Thanks for this patch. Unfortunately, it has one issue: you only took
care of the first-order reverse dependencies of harfbuzz, i.e the
packages that directly select harfbuzz. But you didn't look at the
reverse dependencies of these reverse dependencies. For example, in
this patch, you're changing pango to require gcc >= 4.9. But you didn't
look at the packages that themselves select pango. They also need to be
updated accordingly!


> diff --git a/package/pango/Config.in b/package/pango/Config.in
> index cf5170c8f3..ff529ab0dc 100644
> --- a/package/pango/Config.in
> +++ b/package/pango/Config.in
> @@ -5,7 +5,7 @@ config BR2_PACKAGE_PANGO
>  	depends on BR2_USE_MMU # glib2
>  	depends on BR2_INSTALL_LIBSTDCPP # freetype support
>  	depends on BR2_TOOLCHAIN_HAS_SYNC_4 # harfbuzz
> -	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 # harfbuzz
> +	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # harfbuzz
>  	select BR2_PACKAGE_LIBGLIB2
>  	select BR2_PACKAGE_LIBFRIBIDI
>  	select BR2_PACKAGE_EXPAT

You also forgot to update the Config.in comment in this file.

Could you revisit this and provide an improved version?

Thanks a lot!

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

  reply	other threads:[~2021-11-14 14:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06 18:13 [Buildroot] [PATCH] package/harfbuzz: bump to version 3.1.0 Giulio Benetti
2021-11-08 18:35 ` [Buildroot] [PATCH 0/1] package/harfbuzz: bump to version 3.1.1 Giulio Benetti
2021-11-08 18:35   ` [Buildroot] [PATCH 1/1] " Giulio Benetti
2021-11-14 14:08     ` Thomas Petazzoni [this message]
2021-11-15 18:02       ` [Buildroot] [PATCH v2] " Giulio Benetti

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=20211114150806.2e39e94c@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=corjon.j@ecagroup.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=ps.report@gmx.net \
    --cc=raphael.melotte@mind.be \
    --cc=romain.naour@gmail.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