Description of Problem:
Trying to recompile my own kernel, I found that the build would fail with a message:
error: Installed (but unpackaged) file(s) found:
(and then a list of hundreds of files, many for other architectures)
I figured I had broken something, but the shipping source rpm also fails in the
same way. I understand that this (checking for unpackaged files) is a new RPM
feature, and I understand the reason behind it, but it seems incorrect to me
that the package as shipped by Red Hat does not build on the RPM setup as
shipped by Red Hat.
Am I expected to disable RPM's unpackaged-files check? Why are you bothering to
ship with this check turned on, then, if users will have to turn it off to
actually build anything?
Is there a way to disable this check in the SPEC file?
Version-Release number of selected component (if applicable):
rpm -i <kernel...src.rpm>
rpmbuild -ba <spec-file>
Either add to kernel.spec
or (recommended) clean up $RPM_BUILD_ROOT in %install
You need to install the redhat-rpm-config package to replicate the build environment we
use (which in this case happens to be different from the generic rpm defaults).
I fail to see the point in shipping rpm with less-than-useful settings, since
redhat-rpm-config is not installed by default. I would bet I'm not the last
person who'll be caught off guard by this. But OK, my stuff's working now, so
Note that the correct syntax (thanks jbj) to turn this off in the spec file is:
%define _unpackaged_files_terminate_build 0