lirc-0.8.3 fails patching kernel-2.6.26 Reproducible: Always Steps to Reproduce: 1. emerge (kernel-2.6.26) 2. emerge -u lirc-0.8.3-r2 Actual Results: >>> Unpacking source... >>> Unpacking lirc-0.8.3.tar.bz2 to /var/tmp/portage/app-misc/lirc-0.8.3-r2/work * Applying lirc-0.8.3-kernel-2.6.26.diff ... * Failed Patch: lirc-0.8.3-kernel-2.6.26.diff ! * ( /usr/portage/app-misc/lirc/files/lirc-0.8.3-kernel-2.6.26.diff ) * * Include in your bugreport the contents of: * * /var/tmp/portage/app-misc/lirc-0.8.3-r2/temp/lirc-0.8.3-kernel-2.6.26.diff-6697.out * * ERROR: app-misc/lirc-0.8.3-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 4085: Called epatch 'src_unpack' * environment, line 2096: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: lirc-0.8.3-kernel-2.6.26.diff! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/app-misc/lirc-0.8.3-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/app-misc/lirc-0.8.3-r2/temp/environment'. * It looks like the patch is looking for the top dirs 'a/drivers' and 'b/drivers' from the unpacked lirc tarball. Top dirs 'a' & 'b' don't exist, unless I'm scanning this output wrong.
Created attachment 161449 [details] lirc-0.8.3-kernel-2.6.26.diff-6697.out Patch debug output (diff)
Created attachment 161455 [details, diff] Fixed patch zOMG, it fails on $Id. Adding patch w/o $Id. But loading lirc_serial fails: lirc_serial: no symbol version for lirc_unregister_plugin lirc_serial: Unknown symbol lirc_unregister_plugin lirc_serial: no symbol version for lirc_register_plugin lirc_serial: Unknown symbol lirc_register_plugin
Found some temporary workaround: » http://vdr-portal.de/board/thread.php?postid=738978#post738978
Comment #3 is kind of a hack. If I had time to create a patch, I would. (Only get three months of warm weather here, so I'm completely busy.)
The are cvs keywords like $Id: $ that get modified when commiting the patch :( Removed them and it works like a charm.
Created attachment 161516 [details] patch results Why is this 2.6.26 patch being applied on a system that has 2.6.24? Only gentoo-sources version 2.6.25-r7 is marked as stable at the moment, so wouldn't this version of lirc be better to be still masked? I'll mask this for myself, but might be annoying for other users as well. >>> Emerging (1 of 3) app-misc/lirc-0.8.3-r2 to / * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/2.6.24-gentoo-r4/build * Found sources for kernel version: * 2.6.24-gentoo-r4 * Checking for suitable kernel configuration options... [ ok ] * Compiling support for device irman * * lirc-configure-opts: --with-driver=irman * Setting default lirc-device to /dev/lirc0 * Applying lirc-0.8.3-kernel-2.6.26.diff ... * Failed Patch: lirc-0.8.3-kernel-2.6.26.diff ! * ( /usr/portage/app-misc/lirc/files/lirc-0.8.3-kernel-2.6.26.diff ) * * Include in your bugreport the contents of: * * /var/tmp/portage/app-misc/lirc-0.8.3-r2/temp/lirc-0.8.3-kernel-2.6.26.diff-10621.out
