From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Doug Evans <xdje42@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] testsuite/boards/stabs.exp
Date: Sun, 14 Dec 2014 13:20:00 -0000 [thread overview]
Message-ID: <20141214132031.GQ5457@adacore.com> (raw)
In-Reply-To: <87ioheviwk.fsf@codesourcery.com>
> Alternatively, we can referencehttps://sourceware.org/gdb/wiki/TestingGDB ,
> passing CFLAGS_FOR_TARGET='-gstabs' to dejagnu is convenient too, so I
> don't see the necessity to add a new board file to do that.
Another idea I thought about yesterday was to write a small python
script that takes arguments on the command line and then calls make
the right way for us, potentially even generating board files if
necessary. The interesting bit in the script is the ability to call
it with --help...
--
Joel
next prev parent reply other threads:[~2014-12-14 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 23:46 Doug Evans
2014-12-14 6:42 ` Yao Qi
2014-12-14 7:05 ` Doug Evans
2014-12-14 13:24 ` Joel Brobecker
2014-12-15 3:23 ` Yao Qi
2014-12-15 11:12 ` Pedro Alves
2014-12-17 7:28 ` Doug Evans
2014-12-14 13:20 ` Joel Brobecker [this message]
2014-12-14 17:23 ` Doug Evans
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=20141214132031.GQ5457@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=xdje42@gmail.com \
--cc=yao@codesourcery.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