From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Sat, 07 Apr 2018 17:38:53 +0200 Subject: [Buildroot] [PATCH] busybox: disable PAM in the config if linux-pam is not selected In-Reply-To: <20180326120006.24104-1-arnout@mind.be> (Arnout Vandecappelle's message of "Mon, 26 Mar 2018 14:00:06 +0200") References: <20180326120006.24104-1-arnout@mind.be> Message-ID: <87zi2ff2lu.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) writes: > 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) > --- > Resend, patchwork missed the first send. Committed to 2018.02.x, thanks. -- Bye, Peter Korsgaard