diff options
| author | Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> | 2018-03-26 14:00:06 +0200 |
|---|---|---|
| committer | Peter Korsgaard <peter@korsgaard.com> | 2018-03-26 14:51:08 +0200 |
| commit | 0876b023663377bc3a24c80399f447c1f2afe0c1 (patch) | |
| tree | 18ec7c56ab3a63ca60a10174a8fd08217ee4a1c4 /package/python-docker/python-docker.mk | |
| parent | eaa63edbee8b8bfdac3fcbd84573220c607e0662 (diff) | |
| download | buildroot-0876b023663377bc3a24c80399f447c1f2afe0c1.tar.gz buildroot-0876b023663377bc3a24c80399f447c1f2afe0c1.zip | |
busybox: disable PAM in the config if linux-pam is not selected
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>
Diffstat (limited to 'package/python-docker/python-docker.mk')
0 files changed, 0 insertions, 0 deletions
