0876b02366
Currently there is only logic to enable PAM when linux-pam is selected. However, busybox will fail to build with PAM enabled if the linux-pam package has not been built before. So we should forcibly disable PAM in busybox in that case. Normally this is not an issue since our default busybox config doesn't have PAM enabled. However, if you enable linux-pam, then save the busybox config to a custom configuration file, then disable linux-pam again, and then do a "make clean; make", the build will fail. A more practical situation where this can occur is when the same custom busybox config is used in a Buildroot config with and without linux-pam. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
|---|---|---|
| .. | ||
| 0001-networking-libiproute-use-linux-if_packet.h-instead-.patch | ||
| 0002-Makefile.flags-strip-non-l-arguments-returned-by-pkg.patch | ||
| 0003-tar-unzip-postpone-creation-of-symlinks-with-suspici.patch | ||
| busybox-minimal.config | ||
| busybox.config | ||
| busybox.hash | ||
| busybox.mk | ||
| Config.in | ||
| inittab | ||
| mdev.conf | ||
| S01logging | ||
| S10mdev | ||
| S15watchdog | ||
| S50telnet | ||
| udhcpc.script | ||