Hello Geoff, Thanks for the tip. Very helpful. Discovered with the additional output that there was a file /build/amd64-usr/var/tmp/portage/sys-kernel/coreos-sources-4.6.3/temp/patch-4.6.5-rt9.err that indicates that the patch shall be applied with -p1 but patching of 1 of the internal files failed. But this was an easy fix and it works now. Next step booting a bare metal machine with this kernel and running cyclictest to measure the result.
Greetings Gerrit On Friday, August 5, 2016 at 11:57:45 PM UTC+2, Geoff Levand wrote: > > Hi, > > On Fri, 2016-08-05 at 13:11 -0700, [email protected] <javascript:> > wrote: > > I try to apply the RT patches to the CoreOS kernel. I took the stable > build 1068.8.0 as base and placed patch-4.6.5-rt9.patch as first patch of > the UNIPATCH_LIST in the coreos-sources-4.6.3.ebuild file. > > Logging shows that first the patch-4.6.3.xz will be applied and then the > RT patch, as intended. Unfortunately I get the error: > > die "Unable to dry-run patch on any patch depth lower than 5. > > I have the following questions: what is the causing this error message? > > That message comes from here: > > > https://github.com/coreos/portage-stable/blob/master/eclass/kernel-2.eclass#L1139 > > > > > > If you haven't already you could try something like: > > ECLASS_DEBUG_OUTPUT='on' FEATURES='noclean' emerge-amd64-usr --deep > --verbose --debug sys-kernel/coreos-sources > > I noticed the eclass function debug-print-kernel2-variables. > Maybe adding it in coreos-sources-4.6.3.ebuild will help you. > > -Geoff >
