From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15401] host-rust-1.67.0 does not compile due to missing mallinfo2 and arc4random
Date: Mon, 03 Apr 2023 12:20:55 +0000 [thread overview]
Message-ID: <bug-15401-163-6krGeBxfZc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15401-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15401
alban.at.ifd@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #9546|0 |1
is obsolete| |
--- Comment #5 from alban.at.ifd@gmail.com ---
Created attachment 9571
--> https://bugs.busybox.net/attachment.cgi?id=9571&action=edit
Use the toolchain's vendor string to identify the rustc target.
I uploaded the patch we use to build the toolchain. I only tested it on
2023.02.
This patch add the support of the triplet x86_64-buildroot-linux-gnu into the
rustc source code: It means that if the TARGET_VENDOR variable is set to
somethings else than "buildroot" (via the BR2_TOOLCHAIN_BUILDROOT_VENDOR
option), it will not work.
--
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 prev parent reply other threads:[~2023-04-03 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 9:52 [Buildroot] [Bug 15401] New: host-rust-1.67.0 does not compile due to missing mallinfo2 and arc4random bugzilla
2023-03-17 9:55 ` [Buildroot] [Bug 15401] " bugzilla
2023-03-17 9:55 ` bugzilla
2023-03-21 12:08 ` bugzilla
2023-03-21 12:11 ` bugzilla
2023-03-21 12:12 ` bugzilla
2023-03-21 14:47 ` bugzilla
2023-04-03 12:20 ` bugzilla [this message]
2024-06-15 15:06 ` 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-15401-163-6krGeBxfZc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.