From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] [D] Remove search_parents parameter from d_lookup_symbol_imports
Date: Thu, 29 Oct 2015 17:10:00 -0000 [thread overview]
Message-ID: <CABOHX+dMHKXK6AvNxStHH9qdgcODtT85FjimfcdqTbF3R0QsqA@mail.gmail.com> (raw)
In-Reply-To: <562E5515.2090200@redhat.com>
On 26 October 2015 at 17:30, Pedro Alves <palves@redhat.com> wrote:
> On 10/23/2015 09:35 PM, Iain Buclaw wrote:
>
>> It helps if there is a compiler readily available to compile said
>> tests. However, there likely is a way to get around this that I'm not
>> aware of. (Skip certain tests if a compiler doesn't exist? ;-)
>
> The C, C++, Go, Java, Ada, Fortran and Pascal, etc. tests do get skipped if a
> compiler is not available. I'd hazard a guess that you're missing a
> compiler for at least one of those languages. :-)
>
> If you hook D program building through
> prepare_for_testing/gdb_compile/default_target_compile etc., then D
> tests will behave the same. Basically, tweak lib/future.exp:gdb_default_target_compile
> to understand "d" (and send the equivalent patch to DejaGnu).
>
> See a766d390 for when "go" support was added.
>
> Thanks,
> Pedro Alves
>
I've made a note and will explore that avenue. Thanks!
Iain.
prev parent reply other threads:[~2015-10-29 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 12:01 Iain Buclaw
2015-10-19 15:42 ` Pedro Alves
2015-10-25 11:19 ` Iain Buclaw
2015-10-26 3:47 ` Doug Evans
2015-10-29 17:10 ` Iain Buclaw
2016-01-30 13:50 ` Iain Buclaw
2015-10-26 21:35 ` Pedro Alves
2015-10-29 17:10 ` Iain Buclaw [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=CABOHX+dMHKXK6AvNxStHH9qdgcODtT85FjimfcdqTbF3R0QsqA@mail.gmail.com \
--to=ibuclaw@gdcproject.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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