On Tue, Jan 26, 2016 at 12:04 AM, Michael Hill <mdhillca(a)gmail.com> wrote:
Thanks, Laura. CM3218X is under light sensors, and should be a
The line first gets removed when I run 'make oldconfig,' so I skipped
'make oldconfig.' I still get the same error and it seems to be
introduced in the line 'mv kernel-4.4.0-aarch64.config .config' under
'for i in *.config' in the spec file. I've built kernels before, but
in this case I want to wind up with a Fedora kernel package I can
install and remove cleanly, otherwise I wouldn't be trying to use
rpmbuild. I want an i686 kernel... does my command line look correct?
rpmbuild -bb --with baseonly --without debuginfo --target=i686 kernel.spec
Add the following to config-generic:
# CONFIG_CM3218X is not set
It's not in the upstream kernel so it must be coming from a patch you apply.
> On Mon, Jan 25, 2016 at 11:39 AM, Laura Abbott <labbott(a)redhat.com> wrote:
>> On 01/23/2016 04:57 PM, Michael Hill wrote:
>>> Since the last version of Fedlet came out, I've been building a kernel
>>> package on my Baytrail tablet from the fc24 source rpm following these
>>> This worked for a number of 4.2 kernels as well as a couple of 4.4 rc
>>> kernels. On or about rc6 and continuing with 4.4.0-1, I've been
>>> running this step:
>>> rpmbuild -bb --with baseonly --without debuginfo --target=i686 kernel.spec
>>> ...and (after the patches are applied), failing like this:
>>> Applying: i2c: designware: Convert to use unified device property API
>>> Applying: drm/udl: Use unlocked gem unreferencing
>>> + chmod +x scripts/checkpatch.pl
>>> + touch .scmversion
>>> + mkdir configs
>>> + for i in '*.config'
>>> + mv kernel-4.4.0-aarch64.config .config
>>> ++ head -1 .config
>>> ++ cut -b 3-
>>> + Arch=arm64
>>> + grep -E '^CONFIG_'
>>> + make ARCH=arm64 listnewconfig
>>> + '[' -s .newoptions ']'
>>> + cat .newoptions
>>> + exit 1
>>> error: Bad exit status from /var/tmp/rpm-tmp.niuQ3f (%prep)
>>> RPM build errors:
>>> Bad exit status from /var/tmp/rpm-tmp.niuQ3f (%prep)
>>> a. Is there something obvious I can fix?
>>> b. Is there a better place to ask?
>> That (cryptic) error is indicating that CONFIG_CM3218X needs to be set in a
>> file somewhere. Try adding CONFIG_CM3218X=<whatever> to config-local and
>> build again. You will need to figure out whether <whatever> should be y, n
>> or m
> kernel mailing list