From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/7] gdb: arc: Use git instead of website
Date: Tue, 12 Nov 2013 22:52:50 +0100 [thread overview]
Message-ID: <20131112225250.51c7459b@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D685F1749A@de02wembxa.internal.synopsys.com>
Dear Mischa Jonker,
On Tue, 12 Nov 2013 21:40:12 +0000, Mischa Jonker wrote:
> > Is there any reason why for gdb and binutils we don't have a "choice"
> > option for the ARC version? I know it's a bit silly because for ARC that
> > would be the only choice, but that would make things more similar to what we
> > do for gcc, no?
>
> I think that was decided as part of the review process back then. To be honest, I forgot to remove the choice in gcc now, so I didn't use this opportunity to make it consistent. Now that I'll make a v2 anyway, please let me know what your preference is: to choose or not to choose.
The problem is that the gcc choice is helpful to be able to do the
"select BR2_GCC_NEEDS_MPC". If you remove the gcc version choice, you
would have to add a "select BR2_GCC_NEEDS_MPC if BR2_arc" under the
main gcc option. Not a big deal, but I'm wondering if I don't prefer
having a single choice option.
Let's hear what others have to say, I don't have a really strong
opinion on the matter, except that I'd like to have consistency between
gcc/binutils/uClibc on the matter, and also across architectures: ARC,
AVR32 and Microblaze (all needing special versions) should use the same
strategy. Of course, I'm not asking you to fix all of them, just want
to figure out a strategy that we will apply to all of these cases.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-12 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 13:26 [Buildroot] [PATCH 0/7] RFC: Move to github as source for ARC-specific packages Mischa Jonker
2013-11-12 13:26 ` [Buildroot] [PATCH 1/7] gdb: arc: Use git instead of website Mischa Jonker
2013-11-12 21:37 ` Thomas Petazzoni
2013-11-12 21:40 ` Mischa Jonker
2013-11-12 21:52 ` Thomas Petazzoni [this message]
2013-11-12 13:26 ` [Buildroot] [PATCH 2/7] binutils: " Mischa Jonker
2013-11-12 13:26 ` [Buildroot] [PATCH 3/7] gcc: arc: Download from github instead of Synopsys website Mischa Jonker
2013-11-12 13:26 ` [Buildroot] [PATCH 4/7] uclibc: arc: Use git instead of website Mischa Jonker
2013-11-12 13:26 ` [Buildroot] [PATCH 5/7] gcc: remove ARC-specific patches Mischa Jonker
2013-11-12 17:03 ` Arnout Vandecappelle
2013-11-12 13:26 ` [Buildroot] [PATCH 6/7] uclibc: " Mischa Jonker
2013-11-12 13:26 ` [Buildroot] [PATCH 7/7] Revert "arc: Add option for ARC-specific download site" Mischa Jonker
2013-11-12 14:59 ` [Buildroot] [PATCH 0/7] RFC: Move to github as source for ARC-specific packages Spenser Gilliland
2013-11-12 15:07 ` Thomas De Schampheleire
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=20131112225250.51c7459b@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.