Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Linaro Toolchain for RPI and OABI Issues
Date: Thu, 14 Nov 2019 15:15:03 +0100	[thread overview]
Message-ID: <20191114151503.1e0e291b@gmx.net> (raw)
In-Reply-To: <1573739593129-0.post@n4.nabble.com>

Hello rscr,

On Thu, 14 Nov 2019 07:53:13 -0600 (CST), rscr <rafacrespiramon@gmail.com> wrote:

> Hi Peter,
>
> I have checked if the toolchain was correctly installed and I have used the
> checks that you suggested and I got this:
>
> <http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/Linaro_rpi_toolchain.jpg>

Looks good....

>
> The path that I am using on BR2_TOOLCHAIN_EXTERNAL_PATH is:
>
> ~/rcr/tools/toolchains/linaro/rpi/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf

Last try, use a absolute path here e.g. /home/<your login>/rcr/tools/toolchaines/linaro/rpi/tools/arm-bcm2708/arm-rpi-4.9.3-linux-gnueabihf

>
> Maybe I should have said this before, but I am using Ubuntu in dual boot
> mode, along with Windows 10. Could this affect?

Should not...

Regards,
Peter

>
> Kind Regards,
> Rafa
>
>
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2019-11-14 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12  7:11 [Buildroot] Linaro Toolchain for RPI and OABI Issues rscr
2019-11-12 19:15 ` Peter Seiderer
2019-11-13 13:07   ` rscr
2019-11-13 21:13     ` Peter Seiderer
2019-11-14 13:53       ` rscr
2019-11-14 14:15         ` Peter Seiderer [this message]
2019-11-15  7:27           ` rscr

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=20191114151503.1e0e291b@gmx.net \
    --to=ps.report@gmx.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