From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] gcc on target system issue
Date: Sun, 18 Nov 2012 14:27:03 +0100 [thread overview]
Message-ID: <50A8E227.1090300@mind.be> (raw)
In-Reply-To: <CABtOAfyM4gF-AUi0cNSusC542dxcRps=TM20pJe3RdXWU69AuA@mail.gmail.com>
On 16/11/12 22:59, Alexander Khryukin wrote:
>
>
> 2012/11/16 Thomas Petazzoni <thomas.petazzoni at free-electrons.com <mailto:thomas.petazzoni@free-electrons.com>>
>
>> Dear Alexander Khryukin,
>>
>> On Fri, 16 Nov 2012 01:20:32 +0300, Alexander Khryukin wrote:
>>
>> > I'm trying to build gcc on target but it fails with
>>
>> Why are you trying to build gcc on target? What is the purpose of
>> getting gcc on the target when building a small embedded Linux system
>> with Buildroot?
>>
>> Notice that as per the decisions taken during the last Buildroot
>> Developers Meeting, the possibility of building gcc for the target in
>> Buildroot should soon be deprecated. So there is not a strong interest
>> to fix problems reported by users.
>
>
> Ah, it bad solution to deprecate gcc on target.
Well, the problem is that it is more or less broken (as you can testify), and
that nobody is motivated to invest energy into making it work. If you find the
time and resources to fix and maintain gcc on target, and you have a relevant
use case, then there is a possibility to undeprecate it again.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2012-11-18 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 22:20 [Buildroot] gcc on target system issue Alexander Khryukin
2012-11-16 17:10 ` Alexander Khryukin
2012-11-16 17:30 ` Thomas Petazzoni
2012-11-16 21:59 ` Alexander Khryukin
2012-11-17 8:10 ` Peter Korsgaard
2012-11-17 9:08 ` Alexander Khryukin
2012-11-18 13:27 ` Arnout Vandecappelle [this message]
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=50A8E227.1090300@mind.be \
--to=arnout@mind.be \
--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