From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
isar-users <isar-users@googlegroups.com>,
Uladzimir Bely <ubely@ilbers.de>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [PATCH 1/6] meta-isar: u-boot-starfive-visionfive2: Fix fetching, update to BSP version VF2_v3.0.4
Date: Wed, 12 Jul 2023 12:34:01 +0200 [thread overview]
Message-ID: <f889664a-79fe-9da2-25ab-7e6bd9cf615b@siemens.com> (raw)
In-Reply-To: <77ac9827-843c-1c86-d916-58edec0f0487@ilbers.de>
On 12.07.23 09:41, Anton Mikanovich wrote:
> 04/07/2023 13:36, Jan Kiszka wrote:
>> Yeah, that's why we use snapshot.d.o downstream for RISC-V - with its
>> own problems.
>>
>> Jan
>
> Hello, Jan.
>
> Building out-of-tree modules is still broken with
> linux-starfive_5.15-visionfive2 kernel:
>
> | /usr/bin/make -C /lib/modules/5.15.0-isar+/build M=/<<PKGBUILDDIR>> -j
> 24 modules
> | make[2]: Entering directory '/usr/src/linux-headers-5.15.0-isar+'
> | make[3]: *** No rule to make target 'arch/riscv/kernel/vdso/vdso.lds',
> needed by 'arch/riscv/kernel/vdso/vdso.so.dbg'. Stop.
>
> So we can't even check this target on CI.
>
> Did you try to build out-of-tree modules?
>
Yeah, likely the usual problems of downstream stuff.
I think I had the example modules dropped from the build.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-07-12 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 16:21 [PATCH 0/6] Starfive VisionFive 2 updates Jan Kiszka
2023-06-04 16:21 ` [PATCH 1/6] meta-isar: u-boot-starfive-visionfive2: Fix fetching, update to BSP version VF2_v3.0.4 Jan Kiszka
2023-06-12 7:50 ` Jan Kiszka
2023-07-04 10:02 ` Anton Mikanovich
2023-07-04 10:36 ` Jan Kiszka
2023-07-12 7:41 ` Anton Mikanovich
2023-07-12 10:34 ` Jan Kiszka [this message]
2023-09-18 8:13 ` Jan Kiszka
2023-09-22 4:38 ` Uladzimir Bely
2023-06-04 16:21 ` [PATCH 2/6] meta-isar: starfive-visionfive2: Drop IMAGE_INSTALL from machine config Jan Kiszka
2023-06-04 16:21 ` [PATCH 3/6] meta-isar: starfive-visionfive2: Use kernel DTB Jan Kiszka
2023-06-04 16:21 ` [PATCH 4/6] meta-isar: jh7110-u-boot-spl-tool: Rework Jan Kiszka
2023-06-04 16:21 ` [PATCH 5/6] meta-isar: starfive-visionfive2: Switch to upstream U-Boot Jan Kiszka
2023-06-04 16:21 ` [PATCH 6/6] meta-isar: starfive-visionfive2: Drop obsolete recipes Jan Kiszka
2023-06-04 18:57 ` [PATCH 0/6] Starfive VisionFive 2 updates Jan Kiszka
2023-06-08 2:57 ` MOESSBAUER, Felix
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=f889664a-79fe-9da2-25ab-7e6bd9cf615b@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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