Summary: | app-misc/usbirboy: kernel sources accessed through /lib/modules/`uname -r` | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED DUPLICATE | ||
Severity: | QA | CC: | bugs, esigra, media-tv, n-roeser, virtuousfox |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 251464, 241950 | ||
Attachments: |
Build log
sed Makefile to not use `uname -r` |
Description
Diego Elio Pettenò (RETIRED)
2008-12-08 16:31:51 UTC
Created attachment 174645 [details]
Build log
Created attachment 193560 [details, diff]
sed Makefile to not use `uname -r`
I modified the ebuild to EAPI=2 and added, to src_prepare:
sed -i "s:\$(UNAME):${KV_FULL}:g" ${S}/Makefile || die "sed failed"
*** Bug 239612 has been marked as a duplicate of this bug. *** I do get at a chroot tindeebox image : --- Invalid atom in /etc/portage/package.mask/unstable: <=sci-misc/gt-itm >>> Verifying ebuild manifests >>> Emerging (1 of 1) app-misc/usbirboy-0.3.1-r1 >>> Failed to emerge app-misc/usbirboy-0.3.1-r1, Log file: >>> '/var/log/portage/app-misc:usbirboy-0.3.1-r1:20150226-100955.log' * Package: app-misc/usbirboy-0.3.1-r1 * Repository: gentoo * Maintainer: media-tv@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc kernel_linux userland_GNU * FEATURES: preserve-libs sandbox userpriv usersandbox * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 3.19.0-gentoo ln: failed to create symbolic link ‘Module.symvers’: File exists * Preparing usbirboy module Makefile:30: *** recipe commences before first target. Stop. emake failed and wonder how to avoid such an error ? *** This bug has been marked as a duplicate of bug 250301 *** |