From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@redhat.com, carlton@math.stanford.edu,
gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ vs dos names
Date: Thu, 09 Jan 2003 18:23:00 -0000 [thread overview]
Message-ID: <20030109182323.GA27694@nevyn.them.org> (raw)
In-Reply-To: <200301091752.h09HqDL03494@duracef.shout.net>
On Thu, Jan 09, 2003 at 11:52:13AM -0600, Michael Elizabeth Chastain wrote:
> Michael C lies:
> > Well, the snapshot tarball has testsuite/gdb.*/Makefile files in it,
> > thus there are 8.3 conflicts in every testsuite directory.
>
> Whoops, that is a lie, I was sloppy. David C has a very good point
> about gdb.hp/gdb.stabs.
>
> In the snapshot tarball gdb/testsuite has these subdirectories:
>
> gdb.arch gdb.asm gdb.base gdb.c++ gdb.disasm gdb.hp gdb.java gdb.mi
> gdb.stabs gdb.threads gdb.trace
>
> These subdirectories have 'Makefile' files:
>
> gdb.arch gdb.asm gdb.base gdb.c++ gdb.disasm gdb.java gdb.mi gdb.threads
> gdb.trace
>
> The difference is gdb.hp and gdb.stabs. configure.in handles these
> as conditionally set 'configdirs'. All the other testsuite/gdb.*/Makefile
> files are produced by an AC_OUTPUT line.
Once spotted, easily corrected. Thanks for all the digging. A couple
of other things in here need to be fixed up to; give me a couple of
minutes.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-01-09 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 17:52 Michael Elizabeth Chastain
2003-01-09 18:23 ` Daniel Jacobowitz [this message]
2003-01-09 18:50 ` Daniel Jacobowitz
2003-01-09 18:55 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 20:49 Michael Elizabeth Chastain
2003-01-09 17:33 Michael Elizabeth Chastain
2003-01-09 16:45 Michael Elizabeth Chastain
2003-01-10 20:22 ` Eli Zaretskii
2003-01-09 16:22 Andrew Cagney
2003-01-09 17:24 ` David Carlton
2003-01-09 17:27 ` David Carlton
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=20030109182323.GA27694@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox