Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40826 - [devtools] - makechrootpkg uses wrong headers patch when custom kernel is installed on host machine

Attached to Project: Arch Linux
Opened by John (graysky) - Thursday, 12 June 2014, 20:42 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 12 June 2014, 21:55 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When I am building a module from the AUR in the clean-chroot, makechrootpkg uses /lib/modules/${kernver}/build on my host machine rather than the one inside the chroot.

Example: I have one kernel on my host machine: linux-custom and the corresponding linux-custom-headers. I wish to build rtl8192du-git from the AUR[1] inside a clean chroot. When I issue the `mkarchrootpkg -c -u -r /scratch/.chroot64` command, the script starts but fails because it is trying to find my hosts's /lib/modules/${kernver}/build not the standard 3.14-ARCH version inside the chroot.

1. https://aur.archlinux.org/packages/rtl8192du-git/

Additional info:
* package version(s) 20140510-1

Logfile of the build attached; see line 149 wherein the chroot is trying to /lib/modules/3.14.7-1-custom/build which belongs to my host, whereas it should be using the linux-headers 3.14.6 install the chroot.


Steps to reproduce:
   build.log (8.5 KiB)
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 12 June 2014, 21:55 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Makefile references currently running kernel -- not a bug in makechrootpkg
Comment by Dave Reisner (falconindy) - Thursday, 12 June 2014, 20:50 GMT
The problem is that the Makefile uses the following:

KVER := $(shell uname -r)

You need to override this var in the Makefile. Not at all a bug in makechrootpkg.
Comment by John (graysky) - Thursday, 12 June 2014, 21:54 GMT
Thanks for the tip. Safe to close.

Loading...