From: "Alex Bennée" <alex.bennee@linaro.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: don't block building on AArch64 systems
Date: Wed, 06 Aug 2014 09:23:58 +0100 [thread overview]
Message-ID: <87wqamja43.fsf@linaro.org> (raw)
In-Reply-To: <CAFbHwiRnPZhnXVwZbZreJS-DsO2c8xe1S8=72yH0R7y_bHdFug@mail.gmail.com>
Will Newton writes:
> On Tue, Aug 5, 2014 at 3:20 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Dear Alex Benn?e,
>>
>> On Tue, 5 Aug 2014 14:14:13 +0100, Alex Benn?e wrote:
>>> There is no real reason to disable the building of GDB. I suspect the
>>> original patch (be084204) which added the restriction did so not
>>> realising that AArch64 has had thread support in it's toolchain for some
>>> time.
>>
>> be084204 did not add the AArch64 exception: it only made sure the
>> comments about threads being needed would not be shown on AArch64,
>> because gdb is never available on AArch64.
>>
>> The real commit who made gdb unavailable on AArch64 is
>> 0e49733b306b353aad3a29a2c7a6faf25841ef0b. I believe at the time (April
>> 2013), AArch64 was maybe not supported in the mainline gdb.
My mistake, I got lost in the maze of GDB Config.in changes.
>>
>> Therefore, could you check when AArch64 support was added in mainline
>> gdb ? We currently allow selecting either gdb 7.6 and 7.7 in Buildroot.
>
> AArch64 has been supported since gdb 7.6 (although 7.8 is much nicer
> to use due to bug fixes).
I'll resubmit with a re-worded commit message.
--
Alex Benn?e
next prev parent reply other threads:[~2014-08-06 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 13:14 [Buildroot] [PATCH] gdb: don't block building on AArch64 systems Alex Bennée
2014-08-05 14:20 ` Thomas Petazzoni
2014-08-05 14:46 ` Will Newton
2014-08-06 8:23 ` Alex Bennée [this message]
2014-08-06 10:03 ` 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=87wqamja43.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--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.