Github messages for voidlinux
 help / color / mirror / Atom feed
From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Raspberry Pi: unable to make kernel 5.x scripts
Date: Wed, 11 Nov 2020 11:43:49 +0100	[thread overview]
Message-ID: <20201111104349.r66RniO91Vvi08i5vvTqoRTLIeVnHeCYPRzVCH9UHF8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26257@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2364 bytes --]

Closed issue by ILadis on void-packages repository

https://github.com/void-linux/void-packages/issues/26257

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  `Void 4.19.127_3 armv7l Unknown notuptodate hold rFFF`
* package:  
  `rpi-kernel-headers-5.4.68_1`

### Expected behavior
Upon running `make scripts` from inside `/usr/src/rpi-kernel-headers-5.*` all kernel scripts should be compiled.

Output of `make scripts`:

```
  HOSTCC  scripts/dtc/flattree.o
  HOSTCC  scripts/dtc/fstree.o
  HOSTCC  scripts/dtc/data.o
  HOSTCC  scripts/dtc/livetree.o
  HOSTCC  scripts/dtc/treesource.o
  HOSTCC  scripts/dtc/srcpos.o
  HOSTCC  scripts/dtc/checks.o
  HOSTCC  scripts/dtc/util.o
  HOSTCC  scripts/dtc/dtc-lexer.lex.o
  HOSTCC  scripts/dtc/dtc-parser.tab.o
  HOSTLD  scripts/dtc/dtc
  HOSTCC  scripts/genksyms/genksyms.o
  HOSTCC  scripts/genksyms/parse.tab.o
  HOSTCC  scripts/genksyms/lex.lex.o
  HOSTLD  scripts/genksyms/genksyms
  HOSTCC  scripts/recordmcount
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/pnmtologo
  HOSTCC  scripts/conmakehash
  HOSTCC  scripts/sortextable
  HOSTCC  scripts/asn1_compiler
  HOSTCC  scripts/extract-cert
```

### Actual behavior
Some kernel scripts do not get compiled. No errors occur when running `make scripts` but when I try to compile a kernel module/driver from source it complains about a missing kernel script:

```
Building modules, stage 2.
  MODPOST 1 modules
/bin/sh: 1: scripts/mod/modpost: not found
make[2]: *** [scripts/Makefile.modpost:94: __modpost] Error 127
```

If I then try to explicitly run `make` in `/usr/src/rpi-kernel-headers-5.*/scripts/mod` I get the following error:

```
make: *** No rule to make target '/devicetable-offsets.s', needed by '/devicetable-offsets.h'.  Stop.
```

I do not know if that is the only script that can not be compiled. There may be more missing.

### Steps to reproduce the behavior
Run `cd /usr/src/rpi-kernel-headers-5.* && make scripts` and check if `scripts/mod/modpost` gets compiled.

In order to successfully compile the kernel scripts I had to also install the following development tools:  
`make`, `flex`, `gcc`, `libressl-devel`

  parent reply	other threads:[~2020-11-11 10:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 19:17 [ISSUE] " ILadis
2020-11-09 19:36 ` Anachron
2020-11-09 19:51 ` ILadis
2020-11-09 20:02 ` ILadis
2020-11-09 20:02 ` ILadis
2020-11-09 20:19 ` ILadis
2020-11-09 23:41 ` fosslinux
2020-11-10  0:12 ` pbui
2020-11-10  0:14 ` pbui
2020-11-11 10:43 ` Piraty
2020-11-11 10:43 ` Piraty [this message]
2020-11-11 10:47 ` Piraty
2020-11-15 21:17 ` ILadis
2020-11-15 21:17 ` ILadis
2020-11-15 21:17 ` ILadis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201111104349.r66RniO91Vvi08i5vvTqoRTLIeVnHeCYPRzVCH9UHF8@z \
    --to=piraty@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).