Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yes, I absolutely agree. However, at the moment I don't have a serial cable that I could use.
I have already ordered one, but it will take a few weeks to arrive. I will keep you updated with any news as things happen.
HOSTLD tools/resource_tool
HOSTLD tools/gen_ethaddr_crc
HOSTLD tools/mkenvimage
HOSTLD tools/boot_merger
HOSTLD tools/trust_merger
HOSTLD tools/loaderimage
HOSTLD tools/dumpimage
HOSTLD tools/mkimage
HOSTLD tools/fdtgrep
/home/user/slackbuild/new/b/slackware_arm_build_kit/build/source/arm-trusted-firmware /home/user/slackbuild/new/b/slackware_arm_build_kit/build/source/u-boot-tools
REALCLEAN
CC drivers/arm/gic/common/gic_common.c
CC drivers/arm/gic/v3/arm_gicv3_common.c
CC drivers/arm/gic/v3/gic500.c
CC drivers/arm/gic/v3/gicv3_main.c
CC drivers/arm/gic/v3/gicv3_helpers.c
CC plat/common/plat_gicv3.c
CC plat/rockchip/common/rockchip_gicv3.c
CC drivers/arm/cci/cci.c
CC drivers/delay_timer/delay_timer.c
CC drivers/delay_timer/generic_delay_timer.c
CC drivers/gpio/gpio.c
CC plat/rockchip/common/bl31_plat_setup.c
plat/rockchip/common/bl31_plat_setup.c: In function 'bl31_early_platform_setup2':
plat/rockchip/common/bl31_plat_setup.c:68:29: error: 'console_t {aka struct console}' has no member named 'console'
console_set_scope(&console.console,
^
make: *** [Makefile:966: build/rk3399/release/bl31/bl31_plat_setup.o] Error 1
Edited to add:
The same thing happens if I choose "next" on the second screen.
I believe the arch detection, and download URL determination code may be broken again.
IMHO this URLs would be the proper ones:
Edited to add:
The same thing happens if I choose "next" on the second screen.
I believe the arch detection, and download URL determination code may be broken again.
IMHO this URLs would be the proper ones:
I pulled your latest changes, and retried building the firmware image.
Something still seems to be wrong around the CROSS_COMPILE setting, because I'm still getting the good old familar error message:
Code:
info| start build slarm64 ARCH aarch64
|info| clear boot tools
|info| compiling u-boot-tools next-dev::
|err | details /home/janos/slackbuild/new/c/slackware_arm_build_kit/build/source/build.log
$ tail /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/build.log
#
# configuration written to .config
#
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
UPD include/config.h
CFG u-boot.cfg
GEN include/autoconf.mk.dep
CFG spl/u-boot.cfg
cc1: error: unknown register name: x18 [-Werror]
cc1: error: unknown register name: x18 [-Werror]
cc1: error: unknown register name: x18 [-Werror]
cc1: all warnings being treated as errors
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.autoconf:50: include/autoconf.mk.dep] Error 1
make[1]: *** Waiting for unfinished jobs....
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.autoconf:83: spl/u-boot.cfg] Error 1
make[1]: *** [scripts/Makefile.autoconf:79: u-boot.cfg] Error 1
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/uboot.release'. Stop.
Do you have gcc compiler installed on your system?
Code:
cc --version
Yes, absolutely:
Code:
$ cc --version
cc (GCC) 9.2.0
Copyright (C) 2019 Free Software Foundation, Inc.
Of course it's the x86_64 native version, but the cross compilation toolchain gets automatically downloaded by your script.
I believe the CROSS or CROSS_COMPILE variables may be off. Tomorrow I will have more time to troubleshoot this in more depth.
strange, u-boot-tools do not need a cross-compiler and they must be compiled by the host compiler, since ATF manipulation in the bootloader is given from the host
so it’s clear that this is not connected with compilers and the environment, but with architecture.
Let's check
go to slackware_arm_build_kit/build/source/u-boot-tools
Code:
make clean
make qemu-x86_64_defconfig
make -j6
ls tools/ | grep merge
if everything goes smoothly show the output of the: ls tools/ | grep merge
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
