LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 04-26-2022, 01:21 PM   #1
lazardo
Member
 
Registered: Feb 2010
Location: SD Bay Area
Posts: 270

Rep: Reputation: Disabled
buildroot stage 1 fails at barebox w 'cant find default configuration'


Just noticed that .config contains BR2_KERNEL_HEADERS_5_15=y as specified, whereas buildroot has this in configs/raspberrypi4_64_defconfig:
Code:
# Linux headers same as kernel, a 5.10 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_10=y
. This is current 'buildconfig stable'.

End of update, original follows.

Feels like a top level misconfiguration/omission, but nothing looks out of place to me. Any pointer to start digging appreciated.

First run w buildroot, running under slack 15.0 x86_64 w .34 kernel bump.

The error:
Code:
...
barebox-2021.12.0.tar.bz2: OK (sha256: 555569fe9e71524e0bf927eaa2c1aa2e81ee2c34dd71e39fe21620db6ccc8aa6)
>>> barebox 2021.12.0 Extracting
bzcat /big/arm/buildroot-2022.02.1/dl/barebox/barebox-2021.12.0.tar.bz2 | tar --strip-components=1 -C /big/arm/buildroot-2022.02.1/output/build/barebox-2021.12.0   -xf -
>>> barebox 2021.12.0 Patching
make[1]: Entering directory '/big/arm/buildroot-2022.02.1/output/build/barebox-2021.12.0'
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/confdata.o
  HOSTCC  scripts/kconfig/expr.o
  LEX     scripts/kconfig/lexer.lex.c
  YACC    scripts/kconfig/parser.tab.[ch]
  HOSTCC  scripts/kconfig/menu.o
  HOSTCC  scripts/kconfig/preprocess.o
  HOSTCC  scripts/kconfig/symbol.o
  HOSTCC  scripts/kconfig/util.o
  HOSTCC  scripts/kconfig/lexer.lex.o
  HOSTCC  scripts/kconfig/parser.tab.o
  HOSTLD  scripts/kconfig/conf
***
*** Can't find default configuration "arch/arm/configs/raspberrypi4_64_defconfig"!
***
make[2]: *** [/big/arm/buildroot-2022.02.1/output/build/barebox-2021.12.0/scripts/kconfig/Makefile:94: raspberrypi4_64_defconfig] Error 1
make[1]: *** [Makefile:530: raspberrypi4_64_defconfig] Error 2
make[1]: Leaving directory '/big/arm/buildroot-2022.02.1/output/build/barebox-2021.12.0'
make: *** [boot/barebox/barebox/barebox.mk:9: /big/arm/buildroot-2022.02.1/output/build/barebox-2021.12.0/.stamp_dotconfig] Error 2
Code:
xyzzy@video:/big/arm/buildroot-2022.02.1$ ls -l configs/raspberrypi4_64_defconfig
-rw-r--r-- 1 xyzzy users 1181 Apr 11 14:49 configs/raspberrypi4_64_defconfig

xyzzy@video:/big/arm/buildroot-2022.02.1$ grep raspb .config
BR2_DEFCONFIG="/big/arm/buildroot-2022.02.1/configs/raspberrypi4_64_defconfig"
BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4-64/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4-64/post-image.sh"
BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE="board/raspberrypi4-64/config_4_64bit.txt"
BR2_TARGET_BAREBOX_BOARD_DEFCONFIG="raspberrypi4_64"
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="raspberrypi4_64"
The script was looking for arch/arm/configs/raspberrypi4_64_defconfig, which is not in arch.
Code:
xyzzy@video:/big/arm/buildroot-2022.02.1$ ls -l arch
total 148
-rw-r--r-- 1 xyzzy users 12286 Apr 11 14:49 Config.in
-rw-r--r-- 1 xyzzy users  3190 Apr 11 14:49 Config.in.arc
-rw-r--r-- 1 xyzzy users 28776 Apr 11 14:49 Config.in.arm
-rw-r--r-- 1 xyzzy users  1009 Apr 11 14:49 Config.in.csky
-rw-r--r-- 1 xyzzy users   779 Apr 11 14:49 Config.in.m68k
-rw-r--r-- 1 xyzzy users   431 Apr 11 14:49 Config.in.microblaze
-rw-r--r-- 1 xyzzy users  7295 Apr 11 14:49 Config.in.mips
-rw-r--r-- 1 xyzzy users   309 Apr 11 14:49 Config.in.nds32
-rw-r--r-- 1 xyzzy users   214 Apr 11 14:49 Config.in.nios2
-rw-r--r-- 1 xyzzy users   212 Apr 11 14:49 Config.in.or1k
-rw-r--r-- 1 xyzzy users  5388 Apr 11 14:49 Config.in.powerpc
-rw-r--r-- 1 xyzzy users  2927 Apr 11 14:49 Config.in.riscv
-rw-r--r-- 1 xyzzy users   517 Apr 11 14:49 Config.in.s390x
-rw-r--r-- 1 xyzzy users   798 Apr 11 14:49 Config.in.sh
-rw-r--r-- 1 xyzzy users   848 Apr 11 14:49 Config.in.sparc
-rw-r--r-- 1 xyzzy users 18737 Apr 11 14:49 Config.in.x86
-rw-r--r-- 1 xyzzy users  1367 Apr 11 14:49 Config.in.xtensa
-rw-r--r-- 1 xyzzy users   971 Apr 11 14:49 arch.mk
-rw-r--r-- 1 xyzzy users   541 Apr 11 14:49 arch.mk.arc
-rw-r--r-- 1 xyzzy users   470 Apr 11 14:49 arch.mk.csky
-rw-r--r-- 1 xyzzy users   590 Apr 11 14:49 arch.mk.riscv
-rw-r--r-- 1 xyzzy users  1621 Apr 11 14:49 arch.mk.xtensa
Code:
xyzzy@video:/big/arm/buildroot-2022.02.1$ cat configs/raspberrypi4_64_defconfig 
BR2_aarch64=y
BR2_cortex_a72=y
BR2_ARM_FPU_VFPV4=y

BR2_TOOLCHAIN_BUILDROOT_CXX=y

BR2_SYSTEM_DHCP="eth0"

# Linux headers same as kernel, a 5.10 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_10=y

BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,0b54dbda3cca2beb51e236a25738784e90853b64)/linux-0b54dbda3cca2beb5
1e236a25738784e90853b64.tar.gz"
BR2_LINUX_KERNEL_DEFCONFIG="bcm2711"

# Build the DTB from the kernel sources
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="broadcom/bcm2711-rpi-4-b"

BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y

BR2_PACKAGE_RPI_FIRMWARE=y
BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI4=y
BR2_PACKAGE_RPI_FIRMWARE_CONFIG_FILE="board/raspberrypi4-64/config_4_64bit.txt"

# Required tools to create the SD image
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_PACKAGE_HOST_MTOOLS=y

# Filesystem / image
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
# BR2_TARGET_ROOTFS_TAR is not set
BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4-64/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4-64/post-image.sh"

Last edited by lazardo; 04-26-2022 at 01:47 PM. Reason: new info
 
Old 04-26-2022, 05:04 PM   #2
lazardo
Member
 
Registered: Feb 2010
Location: SD Bay Area
Posts: 270

Original Poster
Rep: Reputation: Disabled
Several more config glibc/5.15 variations failed in a similar context EXCEPT the minimal uclibc raspberry4_64_defconfig.

Note that distcc works with buildroot provided ccache is not enabled in .config.

Last edited by lazardo; 04-27-2022 at 02:12 AM.
 
Old 04-27-2022, 02:58 AM   #3
drmozes
Slackware Contributor
 
Registered: Apr 2008
Distribution: Slackware
Posts: 1,543

Rep: Reputation: 1313Reputation: 1313Reputation: 1313Reputation: 1313Reputation: 1313Reputation: 1313Reputation: 1313Reputation: 1313Reputation: 1313Reputation: 1313
hi

You would be best taking this up with the developers of the barebox project - it's not shipped with Slackware and isn't related to the ARM port.
 
Old 04-28-2022, 07:58 PM   #4
lazardo
Member
 
Registered: Feb 2010
Location: SD Bay Area
Posts: 270

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by drmozes View Post
hi

You would be best taking this up with the developers of the barebox project - it's not shipped with Slackware and isn't related to the ARM port.
buildroot is, in this context, is just a tool so my p1/p2s can have better support moving forward, esp kernel/security patch type rebuilds.

A workable cross-compile setup for the firmware+kernel+application arm environment that can leverage x86 hardware, or other functional equiv., would be nice.

If I didn't run slackware the post wouldn't be here. I considered some of you that have had success beyond 'hello world' might actually be able to point to components that work in the above context.

Cheers,
 
Old 04-29-2022, 11:10 AM   #5
mralk3
Slackware Contributor
 
Registered: May 2015
Distribution: Slackware
Posts: 1,900

Rep: Reputation: 1050Reputation: 1050Reputation: 1050Reputation: 1050Reputation: 1050Reputation: 1050Reputation: 1050Reputation: 1050
There are tools you can use here: https://slackware.uk/slackwarearm/sl...earm-devtools/

Specifically these directories:
  1. slackkit
  2. x-toolchain
  3. minirootfs

There are also ready made images and binaries for u-boot, the installer and recovery images for all supported hardware models:

https://slackware.uk/slackwarearm/pl...ch64/bootware/

In the source directory you can find ready made scripts, tested/used/created by Stuart and myself for building u-boot, installer and recovery images.

The operating system is also extensible for developers or hardware model custodians. Meaning, you can add new single board computers to Slackware ARM64 with all these supporting tools.

AND, if you want to do the same for 32bit Slackware ARM, you can read the source of these shell scripts, and do the same, manually or automatically. I did just that the other day for a Orange Pi R1 with 256MB of RAM. It involved some manual steps, but the same process applies.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Buildroot / ARM - aarch64: Compile of NodeJs fails wolfbiker1 Linux - Software 2 08-30-2021 08:15 AM
[SOLVED] Barebox on Phytec usb drive detection GeneCode Linux - Embedded & Single-board computer 6 08-28-2017 10:08 PM
FC3 installation fails at post install configuration stage grstaker Fedora - Installation 8 06-20-2005 10:43 AM
Half of my applications are broken. I am using Gentoo stage 1 on 3 nptl (stage 1.5) dragonslay Linux - Games 3 04-01-2005 05:23 PM
Gentoo: Stage 1, Stage 2, or Stage 3 skorpi0wn Linux - Distributions 3 03-01-2005 07:47 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 12:13 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration