From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [rfa] doc/gdbint.texinfo: update commands for release tarball
Date: Fri, 10 Jan 2003 05:29:00 -0000 [thread overview]
Message-ID: <200301100529.h0A5TVm14169@duracef.shout.net> (raw)
This patch updates gdbint.texinfo with the new instructions for making
a release tarball.
Note that more people than the release manager need this information.
I wrote this patch because I needed to know how snapshot tarballs were
made in order to debug a problem with testsuite/gdb.c++ files inside
the current snapshots.
Testing: I followed the instructions on a fresh tree and I got some nice
looking tarballs.
OK to apply?
Michael C
2003-01-09 Michael Chastain <mec@shout.net>
* gdb.texinfo (Configuring @value{GDBN} for Release): Update
to "make -f src-release gdb.tar".
Index: gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.115
diff -u -r1.115 gdbint.texinfo
--- gdbint.texinfo 9 Jan 2003 18:46:02 -0000 1.115
+++ gdbint.texinfo 9 Jan 2003 22:16:03 -0000
@@ -5404,14 +5404,16 @@
@file{libiberty}, and so on):
@smallexample
-make -f Makefile.in gdb.tar.gz
+make -f src-release gdb.tar
+version=2003-01-09-cvs
+bzip2 -v -9 -c gdb-$version.tar > gdb-$version.tar.bz2
+gzip -v -9 -c gdb-$version*.tar > gdb-$version.tar.gz
@end smallexample
@noindent
This will properly configure, clean, rebuild any files that are
distributed pre-built (e.g. @file{c-exp.tab.c} or @file{refcard.ps}),
-and will then make a tarfile. (If the top level directory has already
-been configured, you can just do @code{make gdb.tar.gz} instead.)
+and will then make a tarfile.
This procedure requires:
next reply other threads:[~2003-01-10 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 5:29 Michael Elizabeth Chastain [this message]
2003-01-10 6:43 ` Andrew Cagney
2003-01-10 15:27 Michael Elizabeth Chastain
2003-01-10 15:58 ` Andrew Cagney
2003-01-10 16:07 Michael Elizabeth Chastain
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=200301100529.h0A5TVm14169@duracef.shout.net \
--to=mec@shout.net \
--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