From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Cc: ac131313@redhat.com, carlton@math.stanford.edu
Subject: Re: gdb.c++ vs dos names
Date: Thu, 09 Jan 2003 20:49:00 -0000 [thread overview]
Message-ID: <200301092049.h09KnBL06983@duracef.shout.net> (raw)
It seems to work for me. 'make -f src-release gdb.tar' gives
me a tarball with no testsuite/gdb.*/Makefile in it.
Two directories still have both a 'Makefile' and 'Makefile.in'
in the tarball:
% tar tf gdb.tar | grep Makefile
...
utils/sparclite/Makefile.in
utils/sparclite/Makefile
...
utils/wince/Makefile.in
utils/wince/Makefile
...
utils/configure.in does not use AC_OUTPUT so there is some other glitch.
This is probably a bug as the generated Makefile has had all its
variables substituted by the release process.
config/djgpp/fnchange.lst is still missing some legitimate files
in gdb.c++. I will submit a patch for that shortly.
Michael C
===
2003-01-09 Daniel Jacobowitz <drow@mvista.com>
* Makefile.in (ALL_SUBDIRS): New variable.
(subdirs, clean, distclean): Use it.
* gdb.arch/Makefile.in: Clean up Makefile. Remove rules for
regenerating Makefile, since it is generated from the top level.
* gdb.asm/Makefile.in: Likewise.
* gdb.base/Makefile.in: Likewise.
* gdb.c++/Makefile.in: Likewise.
* gdb.disasm/Makefile.in: Likewise.
* gdb.java/Makefile.in: Likewise.
* gdb.mi/Makefile.in: Likewise.
* gdb.threads/Makefile.in: Likewise.
* gdb.trace/Makefile.in: Likewise.
next reply other threads:[~2003-01-09 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 20:49 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
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: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=200301092049.h09KnBL06983@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.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