From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with host packages and DL_TOOLS_DEPENDENCIES
Date: Tue, 10 Dec 2019 23:05:17 +0100 [thread overview]
Message-ID: <20191210230517.25be6a63@windsurf.home> (raw)
Hello,
While working on
https://patchwork.ozlabs.org/project/buildroot/list/?series=147671, I
realized that we have an issue with how DL_TOOLS_DEPENDENCIES is
calculated and host packages.
Here is a snippet of code from package/pkg-generic.mk, inside
inner-generic-package:
ifeq ($$($$($(2)_KCONFIG_VAR)),y)
[...]
ifeq ($$($(2)_SITE_METHOD),svn)
DL_TOOLS_DEPENDENCIES += svn
else ifeq ($$($(2)_SITE_METHOD),git)
DL_TOOLS_DEPENDENCIES += git
else ifeq ($$($(2)_SITE_METHOD),bzr)
DL_TOOLS_DEPENDENCIES += bzr
else ifeq ($$($(2)_SITE_METHOD),scp)
DL_TOOLS_DEPENDENCIES += scp ssh
else ifeq ($$($(2)_SITE_METHOD),hg)
DL_TOOLS_DEPENDENCIES += hg
else ifeq ($$($(2)_SITE_METHOD),cvs)
DL_TOOLS_DEPENDENCIES += cvs
endif # SITE_METHOD
DL_TOOLS_DEPENDENCIES += $$(call extractor-system-dependency,$$($(2)_SOURCE))
[...]
endif
So it means that the DL_TOOLS_DEPENDENCIES calculation is inside the
KCONFIG_VAR_$(2) condition, which means it is only true for target
packages (and a few lucky host packages that have a corresponding
Config.in option).
Due to this, if you have a host package that needs a given extractor,
or bzr, or svn, then it is not listed in DL_TOOLS_DEPENDENCIES, and
will not be checked by the support/dependencies/ logic.
We would need to recursively take into account the dependencies of the
current package while calculating this, so that host packages are
properly accounted for.
What do you think ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
reply other threads:[~2019-12-10 22:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191210230517.25be6a63@windsurf.home \
--to=thomas.petazzoni@bootlin.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 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.