Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] (testsuite/Ada) Add gdb_compile_ada
Date: Thu, 26 Feb 2004 23:02:00 -0000	[thread overview]
Message-ID: <20040226230239.GA8487@nevyn.them.org> (raw)
In-Reply-To: <20040226223742.GH1154@gnat.com>

On Thu, Feb 26, 2004 at 02:37:42PM -0800, Joel Brobecker wrote:
> And then building a typical Ada program will be done using the
> following command:
> 
>         % gnatmake -P$objdir/gdb.ada/gnat_ada -g <src_file> -o <dest>
> 
> where <src_file> is the name of the Ada file (*basename* only)
> and <dest> is the name of the executable (can be basename or fullname,
> it doesn't matter)

Great.

> > Also, gdb_compile_ada may want to remove the incremental files in this
> > case, since the testsuite will not use them.
> 
> gnatmake will. For instance gnatmake won't recompile the test programs
> on subsequent runs, unless the sources have changes. Or if we have two
> test programs depending on the same unit, this unit will only be compiled
> once. I think we should keep them, they are useful.

Well, I'm not so sure that qualifies as useful for the testsuite, but
if they go into gdb.ada I don't care :)

> > > +    lappend options "compiler=gnatmake"
> > 
> > See find_gcc in dejagnu's libgloss.exp.
> 
> Could you explain a bit more what you mean (sorry, dejagnu is still
> new to me, and I have allergic reactions to tcl and expect :-/)?
> Do you means that I should create a new find_gnatmake function and
> then do
> 
>         lappend options "compiler=[find_gnatmake]"
> 
> instead? I think this is the last sticky point to look at before being
> able to properly submit these changes for inclusion.

Aye.  You can put find_gnatmake in gdb.exp for now and submit it to
dejagnu later.

The basic goals of the function are:
  - Find an in-tree gnatmake and pass it appropriate options to run
    from in-tree, for testing a combined tree.
  - Use [transform], which will supply the appropriate cross prefixes.

> load_lib libgloss.exp
> 
> proc gdb_begin {args expected_output} {
>    gdb_test "begin $args" "$expected_output" "begin command"
> }

What's begin do again in your sources?  Also, I'm not sure about the
need for an ada.exp; what else do you expet to go here?

Otherwise it looks reasonable.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-26 23:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 19:56 Joel Brobecker
2004-02-24 22:40 ` Joel Brobecker
2004-02-24 23:08 ` Joel Brobecker
2004-02-25 18:32   ` Joel Brobecker
2004-02-25 20:17     ` Daniel Jacobowitz
2004-02-26 22:37       ` Joel Brobecker
2004-02-26 23:02         ` Daniel Jacobowitz [this message]
2004-03-19  0:09           ` Joel Brobecker
2004-03-03  4:21             ` Joel Brobecker
2004-03-05  4:18             ` Daniel Jacobowitz
2004-03-05  6:03               ` Joel Brobecker
2004-03-05 16:48                 ` Daniel Jacobowitz
2004-03-19  0:09                   ` Daniel Jacobowitz
2004-03-26 23:42                   ` Joel Brobecker
2004-03-26 23:46                     ` Daniel Jacobowitz
2004-03-27  0:07                       ` Joel Brobecker
2004-03-19  0:09                 ` Joel Brobecker
2004-03-19  0:09               ` Daniel Jacobowitz

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=20040226230239.GA8487@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.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