All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex.kanavin@gmail.com>
Subject: [PATCH 01/16] binutils: drop target flex/bison from build dependencies
Date: Wed, 25 Aug 2021 13:37:49 +0200	[thread overview]
Message-ID: <20210825113804.779395-1-alex.kanavin@gmail.com> (raw)

This lengthens dependency chains unnecessarily;
also -native versions are already included in DEPENDS via binutils.inc:

DEPENDS = "flex-native bison-native zlib-native gnu-config-native autoconf-native"

I have also checked that nothing in binutils needs anything from target
sysroots of flex/bison:
https://lists.openembedded.org/g/openembedded-core/message/155131

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
 meta/recipes-devtools/binutils/binutils_2.37.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-devtools/binutils/binutils_2.37.bb b/meta/recipes-devtools/binutils/binutils_2.37.bb
index ff9377049b..7430bf1342 100644
--- a/meta/recipes-devtools/binutils/binutils_2.37.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.37.bb
@@ -1,7 +1,7 @@
 require binutils.inc
 require binutils-${PV}.inc
 
-DEPENDS += "flex bison zlib"
+DEPENDS += "zlib"
 
 EXTRA_OECONF += "--with-sysroot=/ \
                 --enable-install-libbfd \
-- 
2.31.1


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 11:37 Alexander Kanavin [this message]
2021-08-25 11:37 ` [PATCH 02/16] gnu-efi: update 3.0.13 -> 3.0.14 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 03/16] glib-2.0: upgrade 2.68.3 -> 2.68.4 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 04/16] util-linux: upgrade 2.37.1 -> 2.37.2 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 05/16] ccache: upgrade 4.3 -> 4.4 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 06/16] git: upgrade 2.32.0 -> 2.33.0 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 07/16] bind: upgrade 9.16.19 -> 9.16.20 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 08/16] bluez5: upgrade 5.60 -> 5.61 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 09/16] openssh: upgrade 8.6p1 -> 8.7p1 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 10/16] ell: upgrade 0.42 -> 0.43 Alexander Kanavin
2021-08-25 11:37 ` [PATCH 11/16] python3-mako: upgrade 1.1.4 -> 1.1.5 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 12/16] vala: upgrade 0.52.4 -> 0.52.5 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 13/16] libnsl2: upgrade 1.3.0 -> 2.0.0 Alexander Kanavin
2021-08-26 17:22   ` [OE-core] " Khem Raj
2021-08-26 18:10     ` Alexander Kanavin
2021-08-25 11:38 ` [PATCH 14/16] gi-docgen: upgrade 2021.6 -> 2021.7 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 15/16] json-glib: upgrade 1.6.2 -> 1.6.4 Alexander Kanavin
2021-08-25 11:38 ` [PATCH 16/16] harfbuzz: upgrade 2.8.2 -> 2.9.0 Alexander Kanavin

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=20210825113804.779395-1-alex.kanavin@gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.