Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot with linaro-5.2-2015.11-1 toolchain
Date: Thu, 25 Feb 2016 21:15:12 +0100	[thread overview]
Message-ID: <56CF60D0.6060500@gmail.com> (raw)
In-Reply-To: <CAF_dkJB=bcGLC7cTKxz=cDGa12D5DqT4JX-qDDyApjFswtraDQ@mail.gmail.com>

Hello,

Le 25/02/2016 21:02, Patrick Doyle a ?crit :
> arrgghh...nothing seems to be going smoothly today.  Well, some days
> are like that..
> 
> Is buildroot known to work (or not work) with the linaro-5.2-2015.11-1
> toolchain (available at
> https://releases.linaro.org/components/toolchain/binaries/latest-5.2/arm-linux-gnueabihf/)
> specified as an external preinstalled toolchain?

Don't use 5.2-2015.11-1 it's broken use 5.2-2015.11-2 which is already supported
by Buildroot 2016.02-rc2.

See https://bugs.linaro.org/show_bug.cgi?id=1995

> 
> Obviously, I'm asking because it's not working for me.  Things appear
> to start going south when the following command:
> 
> $ arm-linux-gnueabihf-gcc -print-file-name=libc.a
> 
> 
> produces the following output on my system:
> 
> libc.a
> 
> Did I do something wrong when I installed it?  (I just unpacked it into /opt).

Just use latest master or 2016.02-rc archive :p

Best regards,
Romain

> 
> --wpd
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

  parent reply	other threads:[~2016-02-25 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 20:02 [Buildroot] buildroot with linaro-5.2-2015.11-1 toolchain Patrick Doyle
2016-02-25 20:13 ` Patrick Doyle
2016-02-25 20:15 ` Romain Naour [this message]
2016-02-25 20:24   ` Patrick Doyle

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=56CF60D0.6060500@gmail.com \
    --to=romain.naour@gmail.com \
    --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