From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14621] New: RISC-V External Toolchain build fails for latest riscv-gnu-toolchain
Date: Tue, 01 Mar 2022 14:20:11 +0000 [thread overview]
Message-ID: <bug-14621-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14621
Bug ID: 14621
Summary: RISC-V External Toolchain build fails for latest
riscv-gnu-toolchain
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: noahhuetter@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
I want to use the RISC-V GNU toolchain as external toolchain from [1] to use in
buildroot. When I specify it and start the build process, the first package
fails to link with the message
libpthread.so: read failed. Is a directory.
Buildroot creates a symlink in the sysroot of output/host that points to
`../../` which is a directory. On older versions with GCC 8 it works.
riscv-gnu-toolchain: tag: 2022.02.25
buildroot: 2022.02-rc3
host: Linux 3.10.0-1160.42.2.el7.x86_64
[1]: https://github.com/riscv-collab/riscv-gnu-toolchain
--
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
next reply other threads:[~2022-03-01 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 14:20 bugzilla [this message]
2022-07-27 13:45 ` [Buildroot] [Bug 14621] RISC-V External Toolchain build fails for latest riscv-gnu-toolchain bugzilla
2024-06-15 15:00 ` 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-14621-163@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