All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with building Divine; wrong Path
Date: Thu, 11 Sep 2014 23:43:33 +0200	[thread overview]
Message-ID: <20140911234333.19976c3d@free-electrons.com> (raw)
In-Reply-To: <5B70540BA10E7D49BEC1ACD5D4148853540BB0C644@FS-SBS2008.fs-net.local>

Dear Andreas Zeiler,

Please don't top post, thanks!

On Wed, 10 Sep 2014 14:26:06 +0200, Andreas Zeiler wrote:

> thanks for reply. I cannot try this with 2014.08. I know that there
> are many fixes but first I need to merge to 2013.05 because another
> platform has this version and we want to merge these platforms to one.

I understand, but you also need to understand that as volunteers
working in an open-source community, we can hardly spend time
supporting old versions of Buildroot. We very much prefer to focus our
efforts on recent versions, where fixes are benefiting everybody, not
just one person.

> Also I tried with removing toolchain from PATH. This had no effect. I
> also removed the toolchainpath from the menuconfig but then the
> toolchain couldn't been found at all.

Since you're using an external toolchain, I would need the tarball of
this toolchain (upload it somewhere), and then your Buildroot .config
(or a simpler Buildroot .config, as long as it exhibits the problem).

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-09-11 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 12:26 [Buildroot] Problem with building Divine; wrong Path Andreas Zeiler
2014-09-11 21:43 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-09-10  9:22 Andreas Zeiler
2014-09-10 10:23 ` Thomas Petazzoni

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=20140911234333.19976c3d@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 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.