From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External Toolchain: Calculation of SYSROOT_DIR in toolchain/toolchain-external/ext-tool.mk wrong?
Date: Wed, 1 Feb 2012 12:34:47 +0100 [thread overview]
Message-ID: <20120201123447.71e90bc2@skate> (raw)
In-Reply-To: <4666169C600DD24C84F509DC90790D5007629FD42D@DEMCHP99E75MSX.ww902.siemens.net>
Le Wed, 1 Feb 2012 12:20:02 +0100,
"Warlich, Christof" <christof.warlich@siemens.com> a ?crit :
> > Would it be possible to get your external toolchain, so that I could do
> > some testing, and integrate it in my set of external toolchains, so
> > that we keep it working in the future?
>
> Thanks a lot for the offer, but I doubt that it is worth the effort.
Well, if we can't test it, it's going to be hard to improve Buildroot
to support this type of toolchain. If you have solved your specific
problem, it's great, but it would have been ever better to improve the
mainline Buildroot so that other users in your case would find things
working nicely :)
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-02-01 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 8:35 [Buildroot] External Toolchain: Calculation of SYSROOT_DIR in toolchain/toolchain-external/ext-tool.mk wrong? Warlich, Christof
2012-02-01 9:38 ` Thomas Petazzoni
2012-02-01 11:20 ` Warlich, Christof
2012-02-01 11:34 ` Thomas Petazzoni [this message]
2012-02-01 12:30 ` Warlich, Christof
2012-02-01 13:01 ` Thomas Petazzoni
2012-02-01 15:15 ` Grant Edwards
2012-02-01 15:48 ` Warlich, Christof
2012-02-01 15:25 ` Warlich, Christof
2012-02-01 16:16 ` Michael S. Zick
2012-02-01 15:05 ` Thomas De Schampheleire
2012-02-01 15:41 ` Warlich, Christof
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=20120201123447.71e90bc2@skate \
--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.