LinuxQuestions.org
Visit Jeremy's Blog.
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 03-03-2020, 07:59 AM   #61
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled

Quote:
Originally Posted by sndwvs View Post
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
I just tried that with the following results:
Code:
root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-tools# make clean
  CLEAN   spl/u-boot.cfg
  CLEAN   u-boot.cfg
root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-tools# make qemu-x86_64_defconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/zconf.tab.o
In file included from scripts/kconfig/zconf.tab.c:2468:
scripts/kconfig/confdata.c: In function ‘conf_write’:
scripts/kconfig/confdata.c:771:19: warning: ‘%s’ directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
  771 |  sprintf(newname, "%s%s", dirname, basename);
      |                   ^~~~~~
scripts/kconfig/confdata.c:771:19: note: assuming directive output of 7 bytes
scripts/kconfig/confdata.c:771:2: note: ‘sprintf’ output 1 or more bytes (assuming 4104) into a destination of size 4097
  771 |  sprintf(newname, "%s%s", dirname, basename);
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
scripts/kconfig/confdata.c:774:20: warning: ‘.tmpconfig.’ directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
  774 |   sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
      |                    ^~~~~~~~~~~~~~~~~
scripts/kconfig/confdata.c:774:3: note: ‘sprintf’ output between 13 and 4119 bytes into a destination of size 4097
  774 |   sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-tools# make 
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK     include/config.h
  CFG     u-boot.cfg
  GEN     include/autoconf.mk
  GEN     include/autoconf.mk.dep
  CFG     spl/u-boot.cfg
  GEN     spl/include/autoconf.mk
  CHK     include/config/uboot.release
  CHK     include/generated/version_autogenerated.h
  CHK     include/generated/timestamp_autogenerated.h
  UPD     include/generated/timestamp_autogenerated.h
  CC      lib/asm-offsets.s
In file included from include/configs/qemu-x86.h:14,
                 from include/config.h:5,
                 from include/common.h:21,
                 from lib/asm-offsets.c:15:
include/configs/x86-common.h:91: error: "CONFIG_SYS_STACK_SIZE" redefined [-Werror]
   91 | #define CONFIG_SYS_STACK_SIZE   (32 * 1024)
      | 
In file included from ././include/linux/kconfig.h:4,
                 from <command-line>:
include/generated/autoconf.h:153: note: this is the location of the previous definition
  153 | #define CONFIG_SYS_STACK_SIZE 0x200000
      | 
cc1: all warnings being treated as errors
make[1]: *** [Kbuild:44: lib/asm-offsets.s] Error 1
make: *** [Makefile:1350: prepare0] Error 2
root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-tools#
 
Old 03-03-2020, 08:25 AM   #62
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
Hmmm, something seems to be off with gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu:



Code:
root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu/bin# ./aarch64-linux-gnu-gcc
bash: ./aarch64-linux-gnu-gcc: No such file or directory
root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu/bin# ls -l ./aarch64-linux-gnu-gcc
-rwxr-xr-x 1 11827 9000 985504 Mar  3 11:50 ./aarch64-linux-gnu-gcc
root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu/bin# file ./aarch64-linux-gnu-gcc
./aarch64-linux-gnu-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-aarch64.so.1, BuildID[sha1]=0cdc4bdda9aeecdefd65c748ad7441793a56aa10, stripped


root@slackbuild:/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu/bin# file /home/user/gcc-aarch64/bin/aarch64-linux-gcc
/home/user/gcc-aarch64/bin/aarch64-linux-gcc: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, with debug_info, not stripped
The last one being the cross-compiler I compiled myself earlier.
I believe something is fishy here. I tested it by downloading the same package on my desktop and running file on the same binary, and voila:
Code:
root@user-work:/home/user/othernet# file /home/user/.../pinebook_pro/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc
/home/user/b/openwrt/pinebook_pro/gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-gcc: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 2.6.24, BuildID[sha1]=0cdc4bdda9aeecdefd65c748ad7441793a56aa10, stripped
The interpreter is different for some reason on the build machine, and the freshly uncompressed cross-compiler package...
The sha1sum of the two files also differ... I am puzzled.

Last edited by wowbaggerHU; 03-03-2020 at 08:42 AM.
 
Old 03-03-2020, 10:20 AM   #63
sndwvs
Member
 
Registered: Aug 2014
Posts: 942

Rep: Reputation: Disabled
I upgraded to 9.2 in recent commits
 
1 members found this post helpful.
Old 03-04-2020, 08:24 AM   #64
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
I upgraded to 9.2 in recent commits
Could you please explain to me why we are doing this in downloads.sh?

Code:
download_xtools() {
...
        # aarch64 change interpreter path
        [[ $ARCH == aarch64 ]] && change_interpreter_path "$SOURCE/$XTOOLS"
        ((c+=1))
...
}
I am not convinced that this step is needed when using the aarch64 cross-compilation toolchain on an x86_64 host.
It basically breaks the compiler and other related executables making them unrunnable as /lib64/ld-linux-aarch64.so.1 is usually not present on an x86_64 machine.
 
Old 03-04-2020, 10:33 AM   #65
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
I tried disabling that patching I mentioned above, and made u-boot-tools to cross-compile (I have compiled and installed it from SlackBuild too).
This is where it failed (I tried compiling the legacy option):

Code:
  CC      drivers/gpio/gpio.c
  CC      plat/rockchip/common/bl31_plat_setup.c
  CC      plat/rockchip/common/params_setup.c
  CC      plat/rockchip/common/plat_pm.c
  CC      plat/rockchip/common/plat_topology.c
  CC      plat/rockchip/common/aarch64/platform_common.c
  CC      plat/rockchip/common/rockchip_sip_svc.c
  CC      plat/rockchip/rk3399/plat_sip_calls.c
  CC      plat/rockchip/rk3399/drivers/gpio/rk3399_gpio.c
  CC      plat/rockchip/rk3399/drivers/pmu/pmu.c
make -C plat/rockchip/rk3399/drivers/m0 BUILD=/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/build/rk3399/release/m0
make[1]: Entering directory '/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/plat/rockchip/rk3399/drivers/m0'
  CC      src/dram.c
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/arm-none-linux-gnueabihf-gcc -g -mcpu=cortex-m0 -mthumb -Wall -O3 -nostdlib -mfloat-abi=soft -ffunction-sections -fdata-sections -fomit-frame-pointer -fno-common -Iinclude/ -I../../include/shared/ -MMD -MT /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/build/rk3399/release/m0/dram.o -c src/dram.c -o /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/build/rk3399/release/m0/dram.o 
make[1]: /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/arm-none-linux-gnueabihf-gcc: Command not found
make[1]: *** [Makefile:125: /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/build/rk3399/release/m0/dram.o] Error 127
make[1]: Leaving directory '/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/plat/rockchip/rk3399/drivers/m0'
make: *** [plat/rockchip/rk3399/platform.mk:107: build/rk3399/release/m0/rk3399m0.bin] Error 2
I have no idea why it tries to build arm-trusted-firmware with the 32-bit ARM cross-compiler. Could you please explain?

Last edited by wowbaggerHU; 03-04-2020 at 10:38 AM.
 
Old 03-04-2020, 11:08 AM   #66
sndwvs
Member
 
Registered: Aug 2014
Posts: 942

Rep: Reputation: Disabled
and thanks again fixed

Quote:
I have no idea why it tries to build arm-trusted-firmware with the 32-bit ARM cross-compiler. Could you please explain?
assembly for rockchip has a specific moment:

Last edited by sndwvs; 03-04-2020 at 11:26 AM.
 
1 members found this post helpful.
Old 03-05-2020, 03:26 AM   #67
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
Quote:
Originally Posted by wowbaggerHU View Post
Code:
  CC      drivers/gpio/gpio.c
  CC      src/dram.c
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/arm-none-linux-gnueabihf-gcc -g -mcpu=cortex-m0 -mthumb -Wall -O3 -nostdlib -mfloat-abi=soft -ffunction-sections -fdata-sections -fomit-frame-pointer -fno-common -Iinclude/ -I../../include/shared/ -MMD -MT /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/build/rk3399/release/m0/dram.o -c src/dram.c -o /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/arm-trusted-firmware/build/rk3399/release/m0/dram.o 
make[1]: /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/arm-none-linux-gnueabihf-gcc: Command not found
It seems it tries to combine the aarch64 cross-compiler's path with the arm cross-compiler's file name prefix, which is wrong. I believe it's due to this:

Code:
        if [[ $ARCH != "arm" ]] && [[ $XTOOL =~ "arm" ]]; then
            [[ $XTOOLS_ARM_SUFFIX =~ "arm" ]] && _XTOOLS_ARM_SUFFIX=$XTOOLS_ARM_SUFFIX
            message "" "DEBUG" "| $ARCH | $XTOOL | $XTOOLS_ARM_SUFFIX | EEEE"
            export CROSS32="${SOURCE}/$XTOOL/bin/${_XTOOLS_ARM_SUFFIX}-"
        fi
This produces the following output:

Code:
|info| added        configuration file rk3399.conf
|info| DEBUG        | aarch64 | gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf | arm-none-linux-gnueabihf | EEEE
|info| DEBUG        | aarch64 | gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu | arm-none-linux-gnueabihf | EEEE
|info| start        build slarm64 ARCH aarch64
This is due to the compiler name being gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu, as it will match on [[ $XTOOL =~ "arm" ]], which should be checked some other way.
 
Old 03-05-2020, 06:26 AM   #68
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
After fixing the CROSS32 problem, I managed to move forward a bit with the compilation, however it failed again at:

Code:
|info| compiling    arm-trusted-firmware master:commit:22d12c4148c373932a7a81e5d1c59a767e143ac2
|info| compiling    u-boot-pinebook_pro master::
|info| version 
|err | details      /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/build.log
Code:
  OBJCOPY u-boot-nodtb.bin
./"arch/arm/mach-rockchip/make_fit_atf.py" \
arch/arm/dts/rk3399-pinebook-pro.dtb > u-boot.its
start=$(/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-nm u-boot | grep __rel_dyn_start | cut -f 1 -d ' '); end=$(/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-nm u-boot | grep __rel_dyn_end | cut -f 1 -d ' '); tools/relocate-rela u-boot-nodtb.bin 0x00200000 $start $end
  MKIMAGE u-boot.itb
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro /home/janos/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
Image Type:   Rockchip RK33 (SD/MMC) boot image
Init Data Size: 69632 bytes
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/linux-rk3399-legacy /home/janos/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
Reversed (or previously applied) patch detected!  Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file include/media/cec.h.rej
And an extra thought:
You mentioned that u-boot-tools is supposed to be compiled to become a binary that is meant to be run on the machine where the image is being built (x86_64 in this case).
If that is the case, then why do we have this?

Code:
compile_boot_tools() {
    message "" "compiling" "$BOOT_LOADER_TOOLS_DIR $BOOT_LOADER_TOOLS_BRANCH"
    cd $SOURCE/$BOOT_LOADER_TOOLS_DIR >> $LOG 2>&1 || (message "err" "details" && exit 1) || exit 1
    make clean >> $LOG 2>&1 || (message "err" "details" && exit 1) || exit 1
    make ${SOCFAMILY}_defconfig >> $LOG 2>&1 || (message "err" "details" && exit 1) || exit 1
    make $CTHREADS tools >> $LOG 2>&1 || (message "err" "details" && exit 1) || exit 1
}
I mean the SOCFAMILY variable is set up based on your choices in the dialog screens at the beginning, so it doesn't depend on what machine you are building the image on, but the target machine. That approach is flawed, as I end up with building u-boot-tools with the config rk3399_defconfig instead of qemu-x86_64_defconfig.

Last edited by wowbaggerHU; 03-06-2020 at 04:40 AM.
 
Old 03-05-2020, 01:18 PM   #69
sndwvs
Member
 
Registered: Aug 2014
Posts: 942

Rep: Reputation: Disabled
thanks wowbaggerHU,
again fixing paths to cross compilers on x86_64 and aarch64 platforms
 
Old 03-06-2020, 06:56 AM   #70
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
thanks wowbaggerHU,
again fixing paths to cross compilers on x86_64 and aarch64 platforms
Thanks sndwvs! The CROSS32 thing works now okay.
However there still are problems with the patching I showed you in my previous comment. In a clean environment the build will fail due to inappropriate pathces:

Code:
  MKIMAGE u-boot.itb
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
Image Type:   Rockchip RK33 (SD/MMC) boot image
Init Data Size: 69632 bytes
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/linux-rk3399-legacy /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
Reversed (or previously applied) patch detected!  Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file include/media/cec.h.rej
Furthermore I still have to patch compile_boot_tools() with CROSS_COMPILE=${CROSS} as otherwise it will fail the already known "unknown register name: x18" error. I believe this is due to the way how SOCFAMILY is used.

Also, the kernel compilation step asks quite a lot of config related questions (appropriate questions this time, not x86_64 related ones like before), so the kernel config used is likely somewhat outdated.
 
Old 03-06-2020, 11:56 AM   #71
sndwvs
Member
 
Registered: Aug 2014
Posts: 942

Rep: Reputation: Disabled
Quote:
Originally Posted by wowbaggerHU View Post
Thanks sndwvs! The CROSS32 thing works now okay.
However there still are problems with the patching I showed you in my previous comment. In a clean environment the build will fail due to inappropriate pathces:

Code:
  MKIMAGE u-boot.itb
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
Image Type:   Rockchip RK33 (SD/MMC) boot image
Init Data Size: 69632 bytes
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/linux-rk3399-legacy /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
Reversed (or previously applied) patch detected!  Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file include/media/cec.h.rej
Furthermore I still have to patch compile_boot_tools() with CROSS_COMPILE=${CROSS} as otherwise it will fail the already known "unknown register name: x18" error. I believe this is due to the way how SOCFAMILY is used.

Also, the kernel compilation step asks quite a lot of config related questions (appropriate questions this time, not x86_64 related ones like before), so the kernel config used is likely somewhat outdated.
fixed legacy kernel source and use of u-boot-tools
 
Old 03-07-2020, 02:47 PM   #72
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
Thank you sndwvs, things do look so much better now. There is one thing that still fails though: the creation of the kernel package:

Code:
  DTC     arch/arm64/boot/dts/rockchip/rk3399pro-npu-evb-v10.dtb
|info| create       kernel packages
|err | details      /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/build.log
build.log looks like this:

Code:
make[1]: Leaving directory '/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/linux-rk3399-legacy-pinebook_pro'
Image Name:   
Created:      Fri Mar  6 19:06:04 2020
Image Type:   ARM Linux Script (uncompressed)
Data Size:    1290 Bytes = 1.26 KiB = 0.00 MiB
Load Address: 00000000
Entry Point:  00000000
Contents:
   Image 0: 1282 Bytes = 1.25 KiB = 0.00 MiB
|----------- delimiter ----------- "create" "kernel packages" -----------|
  CLEAN   .
  CLEAN   arch/arm64/kernel/vdso
  CLEAN   arch/arm64/kernel
  CLEAN   crypto/asymmetric_keys
  CLEAN   crypto
  CLEAN   drivers/tty/vt
  CLEAN   firmware
  CLEAN   kernel
  CLEAN   lib/raid6
  CLEAN   lib
  CLEAN   security/apparmor
  CLEAN   security/selinux
  CLEAN   usr
  CLEAN   arch/arm64/boot
  CLEAN   arch/arm64/boot/dts/rockchip
  CLEAN   .tmp_versions
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/bin2c
  CC      kernel/bounds.s
gcc: error: unrecognized command line option '-mlittle-endian'
make[1]: *** [Kbuild:20: kernel/bounds.s] Error 1
make: *** [Makefile:1079: prepare0] Error 2
I managed to fix it by applying the following patch.
 
Old 03-07-2020, 03:22 PM   #73
sndwvs
Member
 
Registered: Aug 2014
Posts: 942

Rep: Reputation: Disabled
thanks for testing
 
Old 03-07-2020, 04:04 PM   #74
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
thanks for testing
No problem!
The legacy base image now builds successfully. I will now test the "next", and will try to build the legacy and next xfce images as well later on the weekend.
The next time I will have the opportunity to try and boot these images will be on next Tuesday.
If I encounter any problems with building the images, I will let you know!
 
1 members found this post helpful.
Old 03-08-2020, 03:59 AM   #75
wowbaggerHU
Member
 
Registered: Feb 2017
Location: Hungary
Distribution: Slackware
Posts: 179

Rep: Reputation: Disabled
Quote:
Originally Posted by sndwvs View Post
thanks for testing
Unfortunately patching of the "next" u-boot-pinebook_pro failed:

Code:
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
Image Type:   Rockchip RK33 (SD/MMC) boot image
Init Data Size: 69632 bytes
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
/home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/linux-rk3399-next-pinebook_pro /home/user/slackbuild/new/c/slackware_arm_build_kit/build/source/u-boot-pinebook_pro
|----------- delimiter ----------- "patching" "succeeded 0001-net-smsc95xx-Allow-mac-address-to-be-set-as-a-parame.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded 0002-raid6-add-Kconfig-option-to-skip-raid6-benchmarking.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded RK3328-enable-1512mhz-opp.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded RK3399-enable_1.5_2.0_ghz_cpufreq_opp.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded add-board-nanopi-m4v2.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded add-board-rockpi-s-V3-1-1-arm64-dts-rockchip-add-ROCK-Pi-S-DTS-support.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded add-fusb30x-driver.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded board-nanopi-m4v2-dts-add-sound-card.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded board-nanopi-m4v2-dts-ethernet-tweak.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded board-rockpi4-dts-audio-over-hdmi.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded board-rockpi4-dts-leds.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded board-rockpi4-dts-pcie.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded board-rockpi4-dts-upper-port-host.patch" -----------|
|----------- delimiter ----------- "patching" "succeeded board-rockpis-fixes-for-rk3308-rock-pi-s-dts.patch" -----------|
1 out of 1 hunk FAILED -- saving rejects to file arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts.rej

Last edited by wowbaggerHU; 03-08-2020 at 05:07 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
LXer: Destination Linux 131 - Endeavour OS, Deepin, OnlyOffice, Silverblue, Pinebook Pro, Ubuntu Mate, GPD LXer Syndicated Linux News 0 07-25-2019 06:41 AM
LXer: Linux 5.2, Debian 10, Pinebook Pro, Mageia, Whonix, GRUB, Valve, Zorin, Mint | This Week in Linux 73 LXer Syndicated Linux News 0 07-10-2019 06:43 AM
Video : New PINE64 Products. PineBook Pro, PinePhone, PineCam, PineH64 NicoD SBC Linux - Embedded & Single-board computer 2 02-06-2019 04:37 PM

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

All times are GMT -5. The time now is 04:32 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