Something in the buildroot dependency broke the build process #455
Comments
|
Hi @Doralitze ! Thank you for your detailed issue report. One thing I see is that you seem to be building OpenSBI 1.2, whereas the I could imagine that with the minor version bump, OpenSBI could have moved to a slightly different build system, maybe involving |
|
Hi,
I also tried building it with OpenSBI versions `1.1`, `1.3` and `1.5`. Each time with a clean directory. The resulting build failure was the same all the time.
Doralitze
… Am 06.07.2024 um 00:28 schrieb Gregor Haas ***@***.***>:
Hi @Doralitze <https://github.com/Doralitze> ! Thank you for your detailed issue report. One thing I see is that you seem to be building OpenSBI 1.2, whereas the generic platform is currently configured for OpenSBI 1.1: https://github.com/keystone-enclave/keystone/blob/029a3d1bbabb4808c46ef2c15c0e7e7b4543cd37/overlays/keystone/configs/riscv64_generic_defconfig#L24 <https://github.com/keystone-enclave/keystone/blob/029a3d1bbabb4808c46ef2c15c0e7e7b4543cd37/overlays/keystone/configs/riscv64_generic_defconfig#L24>
I could imagine that with the minor version bump, OpenSBI could have moved to a slightly different build system, maybe involving autoconf or Kconfig based on the build errors you're getting. If you want to use OpenSBI 1.2, you may need to specify the OpenSBI configuration in one of these formats -- I'm unsure personally what this would look like. If you want to use OpenSBI 1.1, I'd recommend cleaning your build directory and rebuilding to see if some stale Buildroot configuration options are inadvertently leading you to build 1.2 instead.
—
Reply to this email directly, view it on GitHub <#455 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNT62FUIDHS54YGZOIPYFTZK4MY3AVCNFSM6AAAAABKNAUZFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGQ3TCNBUGY>.
You are receiving this because you were mentioned.
|
|
I have a similar issue, looking in the build.log, it seems it's not finding g++.
|
That's actually a different issue and can be fixed by enabling the build of a C++ compiler in the toolchain. Insert |
|
Hey @Doralitze, |
|
When I try to build the Keystone on QEMU following tutorial, I also meet the same question. |
Describe the bug
Since this week, the build process for for the
qemu/generictarget does not work anymore. The build process fails at theopensbistage. Changing the version of that dependency from1.2to1.1,1.3or1.5did not yield success. Steps to reproduce:After that, add the following lines to
buildroot/configs/qemu_riscv64_virt_defconfig:and finally issue
make. This should fail at theopensbistage with the following tail ofbuild-generic64/build.log:The files that the build script complains about to be missing are not present indeed. In fact they have not been produced at this point at all, making me think that something with the linux build script or its configuration is off.
Build Failure
If you ran into build problems, please add these information
(1) Results of
git submodule status(2) Your Linux distribution (e.g., Ubuntu 14.04)
6.5.0-41-generic #41~22.04.2-Ubuntu(3) The branch you're working on (e.g.,
masterordev)masterScreenshots or Error Log
Additional context
Besides the patch regarding the configuration file, the installation and repository are clean. The manual hosted here has been followed. This procedure yielded sane results last week but redoing it this week did not work. Yet, rewinding to a commit on
masterthat is older than this week did not fix the issue.The text was updated successfully, but these errors were encountered: