From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] uclibc: enable parallel building of libraries
Date: Mon, 30 Jun 2014 11:37:59 +0200 [thread overview]
Message-ID: <20140630113759.1f8ae8a3@free-electrons.com> (raw)
In-Reply-To: <1404113390.3117.5.camel@abrodkin-8560l.internal.synopsys.com>
Dear Alexey Brodkin,
On Mon, 30 Jun 2014 07:29:50 +0000, Alexey Brodkin wrote:
> Thanks for this.
> Let me look at this issue on AVR32.
>
> Frankly I'd prefer to escape conditions withing "uclibc.mk" - this
> condition will remain for many years until somebody tries to do another
> round of clean-up.
>
> I'll try to find an upstream patch that fixes disclosed issue and put it
> in "package/uclibc/0.9.31.1".
>
> What do you think of this approach?
I personally think it's OK to use $(MAKE) for uClibc >= 0.9.33 and
$(MAKE1) for older versions. We only have 0.9.31 to support AVR32, and
since it's an obsolete architecture, I believe we might propose to
deprecate it during the 2014.08 cycle, so I don't think it's worth
spending time on issues relevant only to 0.9.31. If that's done, then
we'll be able to get rid of 0.9.31 and 0.9.32. I don't think it makes
sense to support such old uClibc releases.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-06-30 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 16:26 [Buildroot] [PATCH v2] uclibc: enable parallel building of libraries Alexey Brodkin
2014-06-29 8:07 ` Thomas De Schampheleire
2014-06-29 9:59 ` Alexey Brodkin
2014-06-29 12:43 ` Thomas De Schampheleire
2014-06-29 16:48 ` Alexey Brodkin
2014-06-29 11:20 ` Thomas Petazzoni
2014-06-30 7:24 ` Thomas Petazzoni
2014-06-30 7:29 ` Alexey Brodkin
2014-06-30 9:37 ` Thomas Petazzoni [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=20140630113759.1f8ae8a3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox