From: Richard Weinberger <richard@nod.at>
To: linux-next@vger.kernel.org
Cc: sameo@linux.intel.com, lee.jones@linaro.org,
Arnd Bergmann <arnd@arndb.de>,
yann.morin.1998@free.fr,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Wolfram Sang <wsa@the-dreams.de>,
"open list:I2C SUBSYSTEM" <linux-i2c@vger.kernel.org>,
user-mode-linux-devel
<user-mode-linux-devel@lists.sourceforge.net>
Subject: unmet direct dependencies in -next
Date: Sun, 9 Aug 2015 11:40:05 +0200 [thread overview]
Message-ID: <55C71FF5.1020902@nod.at> (raw)
Hi!
-next faces some build issues on UML because of unmet direct dependencies.
Mostly due to HAS_IOMEM and I2C.
warning: (MEDIA_SUBDRV_AUTOSELECT && VIDEO_CX231XX && INV_MPU6050_IIO) selects I2C_MUX which has unmet direct dependencies (I2C && HAS_IOMEM)
warning: (ST_IRQCHIP && HIP04_ETH && STMMAC_PLATFORM && DWMAC_IPQ806X && DWMAC_LPC18XX && DWMAC_ROCKCHIP && DWMAC_SOCFPGA && DWMAC_STI && TI_CPSW && PINCTRL_ROCKCHIP &&
PINCTRL_DOVE && POWER_RESET_KEYSTONE && POWER_RESET_SYSCON && POWER_RESET_SYSCON_POWEROFF && S3C2410_WATCHDOG && VIDEO_OMAP3 && VIDEO_S5P_FIMC && RTC_DRV_AT91SAM9 && VIDEO_OMAP4 &&
HWSPINLOCK_QCOM && ATMEL_ST && QCOM_GSBI) selects MFD_SYSCON which has unmet direct dependencies (HAS_IOMEM)
warning: (MEDIA_SUBDRV_AUTOSELECT && VIDEO_CX231XX && INV_MPU6050_IIO) selects I2C_MUX which has unmet direct dependencies (I2C && HAS_IOMEM)
warning: (ST_IRQCHIP && HIP04_ETH && STMMAC_PLATFORM && DWMAC_IPQ806X && DWMAC_LPC18XX && DWMAC_ROCKCHIP && DWMAC_SOCFPGA && DWMAC_STI && TI_CPSW && PINCTRL_ROCKCHIP &&
PINCTRL_DOVE && POWER_RESET_KEYSTONE && POWER_RESET_SYSCON && POWER_RESET_SYSCON_POWEROFF && S3C2410_WATCHDOG && VIDEO_OMAP3 && VIDEO_S5P_FIMC && RTC_DRV_AT91SAM9 && VIDEO_OMAP4 &&
HWSPINLOCK_QCOM && ATMEL_ST && QCOM_GSBI) selects MFD_SYSCON which has unmet direct dependencies (HAS_IOMEM)
For example MFD_SYSCON cannot build on UML as it depends on HAS_IOMEM.
While the symbol MFD_SYSCON has correct dependencies some users of MFD_SYSCON
just issue a "select MFD_SYSCON" and bypass the HAS_IOMEM dependency and causing the build to fail.
This brings me to a question on kconfig itself, wouldn't it be better to just disable a symbol if it has
unmet direct dependencies?
Thanks,
//richard
next reply other threads:[~2015-08-09 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 9:40 Richard Weinberger [this message]
2015-08-10 9:10 ` unmet direct dependencies in -next Lee Jones
2015-08-10 9:14 ` Richard Weinberger
2015-08-10 11:12 ` Michal Marek
2015-08-10 11:24 ` Richard Weinberger
2015-08-10 11:55 ` Wolfram Sang
2015-08-10 11:57 ` Michal Marek
2016-01-02 22:01 ` Richard Weinberger
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=55C71FF5.1020902@nod.at \
--to=richard@nod.at \
--cc=arnd@arndb.de \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=wsa@the-dreams.de \
--cc=yann.morin.1998@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).