On Tuesday, June 27, 2017 at 10:42:51 PM UTC+2, Reg Tiangha wrote:
> On 2017-06-27 1:53 PM, Reg Tiangha wrote:
> > On 2017-06-27 1:37 PM,
> > 0spinboson wrote:
> > 
> >> Thanks. Was already up to date, though, and all gzip-related options were 
> >> enabled (as before). Only change was a new package req 
> >> (elfutils-libelf-devel).
> >> As for new info, I have frustratingly little to offer:
> >> -------------
> >>  mkdir -p 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18
> >> + 
> >> PATH=/sbin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/user/.local/bin:/home/user/bin
> >> + dracut --nomdadmconf --nolvmconf --kmoddir 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64/lib/modules/4.11.7-18.pvops.qubes.x86_64
> >>  --modules 'kernel-modules qubes-vm-simple' --conf /dev/null --confdir 
> >> /var/empty -d 'xenblk xen-blkfront cdrom ext4 jbd2 crc16 dm_snapshot' 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
> >>  4.11.7-18.pvops.qubes.x86_64
> >> Kernel version 4.11.7-18.pvops.qubes.x86_64 has no module directory 
> >> /lib/modules/4.11.7-18.pvops.qubes.x86_64
> >> ldconfig: need absolute file name for configuration file when using -r
> >> dracut: ldconfig might need uid=0 (root) for chroot()
> >> ++ lsinitrd 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
> >>  usr/lib/modules/4.11.7-18.pvops.qubes.x86_64/modules.dep
> >> + modules_dep=
> >> + '[' -z '' ']'
> >> ++ mktemp -d
> >> + tmpdir=/tmp/tmp.0U02gQXJIH
> >> + zcat 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs
> >> + cpio -imd -D /tmp/tmp.0U02gQXJIH
> >>
> >> gzip: 
> >> /home/user/rpmbuild/BUILDROOT/kernel-4.11.7-18.pvops.qubes.x86_64//var/lib/qubes/vm-kernels/4.11.7-18/initramfs:
> >>  not in gzip format
> >> cpio: premature end of archive
> >> + exit 1
> >> error: Bad exit status from /var/tmp/rpm-tmp.MAZxNe (%install)
> >> ----------------
> >> (If there is a way to get more (relevant) information, you'll have to tell 
> >> me where to (start) look(ing), sorry.)
> >>
> > 
> > 
> > Curious:  What is your build environment for this kernel? I only ever
> > use/test FC23 because that's what my dom0 runs, but there have been
> > issues when the compile environment is different (ex. FC25).
> > 
> > I've only ever gotten gzip errors if I completely remove gzip support
> > from my config options, but I've only seen it appear at boot and not at
> > compile time.
> > 
> 
> Also, are you using the 4.11 patches from the Hardened Kernel project? I
> remember rpm generation failing one time (can't remember the exact error
> message) with one version of their patches (it patched in properly and
> successfully compiled, but just died when it came to generating the
> rpms), which eventually got fixed in a later revision. If you're using
> them but haven't updated it recently, their latest version is 4.11.7.a:
> 
> https://github.com/copperhead/linux-hardened/releases
> 
> I also have a branch that tracks just that, which is essentially the
> same as my devel-4.11 branch but just adds in and updates the
> linux-hardened patches as those get released, mainly for convenience:
> 
> https://github.com/rtiangha/qubes-linux-kernel/tree/devel-4.11-hard

It seems building works fine on fc23. Wonder what changed between 6/17 and 
today that fc25 no longer compiles kernels, though.

Wasn't using any patches from the hardening project. 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e5c7979e-9338-45f9-aa6d-7f51aaa65f02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to