From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12691] New: host-rust build fails
Date: Sun, 22 Mar 2020 16:59:21 +0000 [thread overview]
Message-ID: <bug-12691-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12691
Bug ID: 12691
Summary: host-rust build fails
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: eyalroyee at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Unable to build host-rust (version 1.33.0).
I'm trying to build host-rust on my Ubuntu 18.04 with buildroot on branch
master (commit 35e845700fb15b4ab30678c073300b508db4eb95)
Steps to reproduce are:
1) select host-rust
2) make host-rust
The error is the following:
failed to parse TOML configuration 'config.toml': expected a table key, found a
right bracket at line 15
failed to run:
/home/eyal/buildroot/output/build/host-rust-1.33.0/build/bootstrap/debug/bootstrap
build
It looks like the HOST_RUST_CONFIGURE_CMDS didn't generated a proper .toml
file.
The 15th line in the generated .toml file is of the following format:
echo '[target.$(RUSTC_TARGET_NAME)]';
I guess that should be some sort of validation for that variable before
evaluating it.
Thanks,
Eyal
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-03-22 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 16:59 bugzilla at busybox.net [this message]
2020-03-22 19:51 ` [Buildroot] [Bug 12691] host-rust build fails bugzilla at busybox.net
2020-03-23 0:27 ` bugzilla at busybox.net
2020-03-23 20:17 ` bugzilla at busybox.net
2020-05-08 15:47 ` bugzilla at busybox.net
2020-05-17 19:23 ` bugzilla at busybox.net
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-12691-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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