From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, carlton@math.stanford.edu
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ vs dos names
Date: Thu, 09 Jan 2003 16:45:00 -0000 [thread overview]
Message-ID: <200301091645.h09GjCw02160@duracef.shout.net> (raw)
If you look in config/djgpp/fnchange.lst, every file in
testsuite/gdb.c++ is in there. I presume it's because of the gdb.c++.
All the new files like pr-574.exp need to be registered.
But I'm looking at my source+build directories for gcc_5_3-branch and
HEAD and I don't see any difference with 'Makefile.in' and 'Makefile'.
In both branch and trunk:
source dir for testsuite/gdb.c++ has a 'Makefile.in'
build dir for testsuite/gdb.c++ has a 'Makefile'
So I don't know why ari.doschk.bug has this for message for HEAD
and does not have it for gcc_5_3_branch.
Andrew C:
> I suspect that the new makefile stuff is forgetting to clean it up after
> a configure? (The script is run over a release, and not the files
> checked out of CVS).
Ermmm, it looks like an interaction between new makefile stuff and the
release process, neither of which I know very well.
Michael C
next reply other threads:[~2003-01-09 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 16:45 Michael Elizabeth Chastain [this message]
2003-01-10 20:22 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 20:49 Michael Elizabeth Chastain
2003-01-09 17:52 Michael Elizabeth Chastain
2003-01-09 18:23 ` Daniel Jacobowitz
2003-01-09 18:50 ` Daniel Jacobowitz
2003-01-09 18:55 ` Andrew Cagney
2003-01-09 17:33 Michael Elizabeth Chastain
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=200301091645.h09GjCw02160@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--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