linux-kernel - Why is arch/s390/crypto/Kconfig sourced when building for another arch ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <eueg41$j5t$1@sea.gmane.org>
Date:	Wed, 28 Mar 2007 22:36:38 +0300
From:	Thomas Backlund <tmb@...driva.org>
To:	linux-kernel@...r.kernel.org
Subject:  Why is arch/s390/crypto/Kconfig sourced when building for another
 arch ?

Hi,

Why is arch/s390/crypto/Kconfig sourced when building for another arch ?

I'm trying to package a stripped down version of the kernelsource with 
only arch-specific code (/arch/$arch & /include/asm-$arch), the rest of 
/include, the whole KBuild setup & contents of /scripts to build 
3rdparty drivers against...

With the above files I can do a:
mv .config config.temp
make mrproper
mv config.temp .config
make oldconfig prepare scripts

and the tree stays intact ...

with 2.6.20.4 it works great, but when switching to 2.6.21-rcX it breaks 
with this:

drivers/crypto/Kconfig:55: can't open file "arch/s390/crypto/Kconfig"

I tried to fix drivers/crypto/Kconfig by changing the code to:

if S390
source "arch/s390/crypto/Kconfig"
endif

but it still gets sourced...

Now, since this is the only arch messing up (atleast on ix86 & x86_64),
shouldn't this be fixed somehow ?

--
Thomas

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/