All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 21 Mar 2023 12:08:25 +0000	[thread overview]
Message-ID: <bug-15401-163-fhIWBjEHzW@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15401-163@https.bugs.busybox.net/>

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

--- Comment #2 from alban.at.ifd@gmail.com ---
> I am suprised to see here that the cross-compiler was defined as cc in the generated config.toml, as we want to build a rust compiler which can be executed on the host system, not on the target system.

To give an answer to my question: we need to give the cross-compiler compiler
in the cc attribute of config.toml. As this compiler will be used to compile
the "shims" written in C which will run on the target. Can somebody confirm it
?

Would be a solution to replace the "unknown" in RUSTC_TARGET_NAME value (set in
rustc.mk) by the value of BR2_TOOLCHAIN_BUILDROOT_VENDOR ? With a different
vendor string, the rustc's bootstrap program would be able to make the
difference between the host and the target toolchains, even if the triplets are
the same.

I wrote a patch which implement this solution. But the drawback seem to be that
the rust-bin package could only be used as stage0 now.

-- 
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

  parent reply	other threads:[~2023-03-21 12:08 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 [this message]
2023-03-21 12:11 ` bugzilla
2023-03-21 12:12 ` bugzilla
2023-03-21 14:47 ` bugzilla
2023-04-03 12:20 ` bugzilla
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-fhIWBjEHzW@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.