On Tue, May 05, 2015 at 05:44:21PM -0700, Luis R. Rodriguez wrote: > From: "Luis R. Rodriguez" <[email protected]> > > We're going to add firmware module signing support, but when we do > this we end up with the following recursive dependency. Fix this by > just depending on FW_LOADER, which is typically always enabled > anyway. > > mcgrof@ergon ~/linux-next (git::master)$ make allnoconfig > scripts/kconfig/conf --allnoconfig Kconfig > crypto/Kconfig:15:error: recursive dependency detected! > crypto/Kconfig:15: symbol CRYPTO is selected by SYSDATA_SIG > init/Kconfig:1880: symbol SYSDATA_SIG is selected by FIRMWARE_SIG > drivers/base/Kconfig:88: symbol FIRMWARE_SIG depends on FW_LOADER > drivers/base/Kconfig:80: symbol FW_LOADER is selected by CRYPTO_DEV_QAT > drivers/crypto/qat/Kconfig:1: symbol CRYPTO_DEV_QAT is selected by > CRYPTO_DEV_QAT_DH895xCC > drivers/crypto/qat/Kconfig:13: symbol CRYPTO_DEV_QAT_DH895xCC depends on > CRYPTO
This doesn't look like a real cycle to me so perhaps we can fix kbuild to understand this? Cheers, -- Email: Herbert Xu <[email protected]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
