| Summary: | sys-power/tuxedo-cc-wmi-0.1.4 : ln: failed to create symbolic link Module.symvers: File exists | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Marc Schiffbauer <mschiff> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tbz2 sys-power:tuxedo-cc-wmi-0.1.4:20200629-233945.log temp.tbz2 |
||
Created attachment 647130 [details]
emerge-info.txt
Created attachment 647132 [details]
emerge-history.txt
Created attachment 647134 [details]
environment
Created attachment 647136 [details]
etc.portage.tbz2
Created attachment 647138 [details]
sys-power:tuxedo-cc-wmi-0.1.4:20200629-233945.log
Created attachment 647140 [details]
temp.tbz2
I dont see a bug here. Sure the ln error is not nice. But not a problem IMO. Do you have any suggested solution? well, seems the real error which stops portage happens later: ln: failed to create symbolic link 'Module.symvers': File exists * Preparing tuxedo_cc_wmi module make -j1 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' CC=x86_64-pc-linux-gnu-gcc KERN_DIR=/usr/src/linux KERN_VER=5.7.5-gentoo O=/usr/src/linux V=1 KBUILD_VERBOSE=1 all make -C /lib/modules/5.7.6/build M=/var/tmp/portage/sys-power/tuxedo-cc-wmi-0.1.4/work/tuxedo-cc-wmi-0.1.4 modules make[1]: *** /lib/modules/5.7.6/build: No such file or directory. Stop. make: *** [Makefile:26: all] Error 2 * ERROR: sys-power/tuxedo-cc-wmi-0.1.4::gentoo failed (compile phase): * emake failed Ah! Then I think it is a missing DEPEND on linux-headers I doubt this will fix it. The problem is propably that you have no kernel installed in the tinderbox? Normally that missing build-symlink is installed by "make modules-install" when kernel modules are being installed. But I dont see how this could be solved in the ebuild well, I do emerge the Gentoo sources and do compile them (make defconfig; make), but yes, I do not *install* them. (Never did it before, it was sufficient to have the kernel and modules just being compiled till now). I can change the tinderbox behaviour install them if really needed, but the question is, why it worked before? I now understand the problem: the provided Makefile uses a (uncommon?) variable "KDIR" which defaults to "/lib/modules/$(shell uname -r)/build". "build" is a distro-independent symlink pointing to the kernel source tree. I will update this (and the other) ebuild to set KDIR properly which will fix the problem. So everything should be fine with your tinderbox! Thanks The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=edd3344582c85ab8d5c5224b6b7b65256ea6f7b2 commit edd3344582c85ab8d5c5224b6b7b65256ea6f7b2 Author: Marc Schiffbauer <mschiff@gentoo.org> AuthorDate: 2020-06-30 14:37:31 +0000 Commit: Marc Schiffbauer <mschiff@gentoo.org> CommitDate: 2020-06-30 14:38:07 +0000 sys-power/tuxedo-cc-wmi: fix bug #730208 Closes: https://bugs.gentoo.org/730208 Package-Manager: Portage-2.3.99, Repoman-2.3.23 Signed-off-by: Marc Schiffbauer <mschiff@gentoo.org> sys-power/tuxedo-cc-wmi/tuxedo-cc-wmi-0.1.4.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) |
>>> Source configured. >>> Compiling source in /var/tmp/portage/sys-power/tuxedo-cc-wmi-0.1.4/work/tuxedo-cc-wmi-0.1.4 ... ln: failed to create symbolic link 'Module.symvers': File exists * Preparing tuxedo_cc_wmi module make -j1 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' CC=x86_64-pc-linux-gnu-gcc KERN_DIR=/usr/src/linux KERN_VER=5.7.5-gentoo O=/usr/src/linux V=1 KBUILD_VERBOSE=1 all make -C /lib/modules/5.7.6/build M=/var/tmp/portage/sys-power/tuxedo-cc-wmi-0.1.4/work/tuxedo-cc-wmi-0.1.4 modules ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-libressl-20200623-041854 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.1.0 * clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python3.6 (fallback) [5] python2.7 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.44.1 * The following VMs are available for generation-2: *) IcedTea JDK 3.16.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.0.2 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Mon 29 Jun 2020 10:35:22 PM UTC /var/db/repos/libressl Fri 19 Jun 2020 10:37:45 AM UTC emerge -qpvO sys-power/tuxedo-cc-wmi [ebuild N ] sys-power/tuxedo-cc-wmi-0.1.4