Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15793] beaglev_defconfig: Cross binutils/gcc configuration problem?
Date: Sun, 24 Sep 2023 18:00:12 +0000	[thread overview]
Message-ID: <bug-15793-163-LrUVtHC8gJ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15793-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15793

--- Comment #1 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
A similar issue exists for beaglev_defconfig:

[build 2023-09-23 10:34:44] mkdir -p `dirname
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/build/lib/sbi/sbi_tlb.o`;
echo " CC        lib/sbi/sbi_tlb.o";
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/host/bin/riscv64-buildroot-linux-gnu-gcc
-g -Wall -Werror -ffreestanding -nostdlib -fno-stack-protector
-fno-strict-aliasing -O2 -fno-omit-frame-pointer -fno-optimize-sibling-calls
-mno-save-restore -mstrict-align -mabi=lp64 -march=rv64imafdc -mcmodel=medany
-I/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/platform/generic/include
-I/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/include
-I/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/lib/utils/libfdt/
 -DFW_PIC -DFW_TEXT_START=0x80000000
-DFW_FDT_PATH=\"/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/images/u-boot.dtb\"
-DFW_JUMP_ADDR=0x80200000 -DFW_JUMP_FDT_ADDR=0x82200000
-DFW_PAYLOAD_PATH=\"/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/images/u-boot.bin\"
-DFW_PAYLOAD_OFFSET=0x200000 -DFW_PAYLOAD_FDT_ADDR=0x82200000  -fno-pie -no-pie
-fPIE -pie
-I/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/lib/sbi
-D__OBJNAME__=sbi_tlb -c
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/lib/sbi/sbi_tlb.c
-o
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/build/lib/sbi/sbi_tlb.o
[build 2023-09-23 10:34:44]  CC        lib/sbi/sbi_tlb.o
[build 2023-09-23 10:34:45]
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/lib/sbi/sbi_tlb.c:
Assembler messages:
[build 2023-09-23 10:34:45]
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/lib/sbi/sbi_tlb.c:175:
Error: unrecognized opcode `fence.i', extension `zifencei' required
[build 2023-09-23 10:34:45] make[1]: *** [Makefile:339:
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/build/lib/sbi/sbi_tlb.o]
Error 1
[build 2023-09-23 10:34:45] make[1]: Leaving directory
'/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom'
[build 2023-09-23 10:34:45] make: *** [package/pkg-generic.mk:293:
/var/lib/laminar/run/buildroot-beaglev_defconfig/6/buildroot/output/build/opensbi-custom/.stamp_built]
Error 2

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-09-24 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 22:36 [Buildroot] [Bug 15793] New: beaglev_defconfig: Cross binutils/gcc configuration problem? bugzilla
2023-09-24 18:00 ` bugzilla [this message]
2023-09-24 18:17 ` [Buildroot] [Bug 15793] " bugzilla
2024-06-15 15:12 ` bugzilla

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=bug-15793-163-LrUVtHC8gJ@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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