All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Corcoles <alex@corcoles.net>
To: buildroot@busybox.net
Subject: [Buildroot] "PATCH": hack to be able to build Rust targetting MIPS
Date: Sun, 19 Jan 2020 20:40:39 +0100	[thread overview]
Message-ID: <CAPAYC_zexzuMfp9F=d8KL-jS8TxQF1sqh07W_zT9J9AiK0rjgA@mail.gmail.com> (raw)
In-Reply-To: <20200118212756.GG32369@scaer>

> RUSTC_TARGET_NAME is defined in package/rustc/rustc.mk:
>
>     10 ifeq ($(BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS),y)
>     11 RUSTC_TARGET_NAME = $(RUSTC_ARCH)-unknown-linux-gnu$(RUSTC_ABI)
>     12 endif
>
> So, it is only defined if BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS is
> set, and this is defined in package/rustc/Config.in.host. It needs a
> glibc toolchain (and an x86 or x86_64 host machine).
>
> But your configuration uses uClibc-ng, not glibc, so this is the reason
> that it does not work for you.
>
> If you believe the dependency on glibc is too stringent, then this is
> the place to fix stuff, not redefine the variable as you suggested.
>

Honestly, I don't have any idea what I'm doing :)

Rust itself supports uclibc on mipsel:

https://forge.rust-lang.org/release/platform-support.html

mipsel-unknown-linux-uclibc is a Tier 3 platform, which is not awesome, but
it could work. Frankly I don't know much about buildroot to hack this up
(or even to know if it's worth trying).

(I'm just trying to run rust-sdl/rust-sdl2 on a RG-300 which uses buildroot
for development purposes. I've managed to build C stuff using SDL
successfully in buildroot, but Rust is proving to be more complex)

-- 
   ___
 {~._.~}
  ( Y )
 ()~*~()  mail: alex at corcoles dot net
 (_)-(_)  http://alex.corcoles.net/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200119/a183a471/attachment.html>

  reply	other threads:[~2020-01-19 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPAYC_xPtDO=j3fWeOEbC41X3PXJZ+7AD=WRm8A1DGQrtbadFQ@mail.gmail.com>
2020-01-18 18:46 ` [Buildroot] "PATCH": hack to be able to build Rust targetting MIPS Alex Corcoles
2020-01-18 19:58   ` Alex Corcoles
2020-01-18 21:27   ` Yann E. MORIN
2020-01-19 19:40     ` Alex Corcoles [this message]
2020-01-19 21:31   ` Eric Le Bihan
2020-01-20 16:31     ` Alex Corcoles
2020-02-03 17:08       ` Alex Corcoles
2020-02-03 17:14         ` [Buildroot] Fwd: " Alex Corcoles
2020-02-05 17:21         ` [Buildroot] " Alex Corcoles
2020-02-06 17:18           ` Alex Corcoles
2020-02-06 17:50             ` Vincent Fazio
2020-02-06 18:00               ` Alex Corcoles

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='CAPAYC_zexzuMfp9F=d8KL-jS8TxQF1sqh07W_zT9J9AiK0rjgA@mail.gmail.com' \
    --to=alex@corcoles.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 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.