From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: get rid of ARC's uClibc fork
Date: Tue, 27 Oct 2015 23:28:55 +0100 [thread overview]
Message-ID: <562FFAA7.9000205@mind.be> (raw)
In-Reply-To: <20151027225741.333ad3f6@free-electrons.com>
On 27-10-15 22:57, Thomas Petazzoni wrote:
> Arnout,
>
> On Tue, 27 Oct 2015 20:13:54 +0100, Arnout Vandecappelle wrote:
>> On 27-10-15 16:16, Alexey Brodkin wrote:
>>> For quite some time all ARC changes have been pushed upstream.
>>> So both uClibc master branch
>>
>> In that case, perhaps the snapshot version should be enabled for ARC?
>
> To be honest, I am wondering if this snapshot thing is really useful in
> any way. Is anyone really using this ? Why do we have this for uClibc
> and not for any other package ?
I guess because buildroot was started as a build system for uClibc... The
initial version of buildroot (ffde94bd2) even only supported snapshot.
Now that there are actual releases of uClibc, I see little reason to support
snapshots. And you anyway can still use _OVERRIDE_SRCDIR.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-10-27 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:16 [Buildroot] [PATCH] uclibc: get rid of ARC's uClibc fork Alexey Brodkin
2015-10-27 19:13 ` Arnout Vandecappelle
2015-10-27 21:57 ` Thomas Petazzoni
2015-10-27 22:28 ` Arnout Vandecappelle [this message]
2015-10-27 22:47 ` Peter Korsgaard
2015-10-27 19:52 ` Waldemar Brodkorb
2015-10-27 21:09 ` Peter Korsgaard
2015-10-27 21:57 ` 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=562FFAA7.9000205@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