* [commit/branch] Update GDB version in README
@ 2007-09-19 19:49 Joel Brobecker
0 siblings, 0 replies; 7+ messages in thread
From: Joel Brobecker @ 2007-09-19 19:49 UTC (permalink / raw)
To: gdb-patches
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
Hello,
In preparation for the upcoming GDB 6.6.90 pre-release, I have
adjusted the version number in the README file.
2007-09-19 Joel Brobecker <brobecker@adacore.com>
* README: Update GDB version number to 6.6.90.
--
Joel
[-- Attachment #2: readme_version.diff --]
[-- Type: text/plain, Size: 11298 bytes --]
Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.41
diff -u -p -r1.41 README
--- README 13 Apr 2007 14:17:46 -0000 1.41
+++ README 19 Sep 2007 19:47:23 -0000
@@ -1,5 +1,5 @@
- README for gdb-6.3 release
- Updated 20, November, 2006
+ README for gdb-6.6.90 release
+ Updated 19, September, 2007
This is GDB, the GNU source-level debugger.
@@ -20,7 +20,7 @@ Unpacking and Installation -- quick over
In this release, the GDB debugger sources, the generic GNU include
files, the BFD ("binary file description") library, the readline
library, and other libraries all have directories of their own
-underneath the gdb-6.3 directory. The idea is that a variety of GNU
+underneath the gdb-6.6.90 directory. The idea is that a variety of GNU
tools can share a common copy of these things. Be aware of variation
over time--for example don't try to build gdb with a copy of bfd from
a release other than the gdb release (such as a binutils release),
@@ -29,8 +29,8 @@ Configuration scripts and makefiles exis
directory tree and automatically build all the pieces in the right
order.
- When you unpack the gdb-6.3.tar.gz file, you'll find a directory
-called `gdb-6.3', which contains:
+ When you unpack the gdb-6.6.90.tar.gz file, you'll find a directory
+called `gdb-6.6.90', which contains:
COPYING config-ml.in gettext.m4 ltconfig sim
COPYING.LIB config.guess include ltmain.sh src-release
@@ -43,7 +43,7 @@ called `gdb-6.3', which contains:
You can build GDB right in the source directory:
- cd gdb-6.3
+ cd gdb-6.6.90
./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
@@ -57,25 +57,25 @@ You can build GDB in any empty build dir
mkdir build
cd build
- <full path to your sources>/gdb-6.3/configure
+ <full path to your sources>/gdb-6.6.90/configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
-different; see the file gdb-6.3/gdb/config/djgpp/README for details.)
+different; see the file gdb-6.6.90/gdb/config/djgpp/README for details.)
This will configure and build all the libraries as well as GDB. If
`configure' can't determine your system type, specify one as its
argument, e.g., `./configure sun4' or `./configure decstation'.
- Make sure that your 'configure' line ends in 'gdb-6.3/configure':
+ Make sure that your 'configure' line ends in 'gdb-6.6.90/configure':
- /berman/migchain/source/gdb-6.3/configure # RIGHT
- /berman/migchain/source/gdb-6.3/gdb/configure # WRONG
+ /berman/migchain/source/gdb-6.6.90/configure # RIGHT
+ /berman/migchain/source/gdb-6.6.90/gdb/configure # WRONG
The gdb package contains several subdirectories, such as 'gdb',
'bfd', and 'readline'. If your 'configure' line ends in
-'gdb-6.3/gdb/configure', then you are configuring only the gdb
+'gdb-6.6.90/gdb/configure', then you are configuring only the gdb
subdirectory, not the whole gdb package. This leads to build errors
such as:
@@ -113,7 +113,7 @@ documentation and TeX (or `texi2roff') t
GDB includes an already formatted copy of the on-line Info version
of this manual in the `gdb/doc' subdirectory. The main Info file is
-`gdb-6.3/gdb/doc/gdb.info', and it refers to subordinate files
+`gdb-6.6.90/gdb/doc/gdb.info', and it refers to subordinate files
matching `gdb.info*' in the same directory. If necessary, you can
print out these files, or read them with any editor; but they are
easier to read using the `info' subsystem in GNU Emacs or the
@@ -125,7 +125,7 @@ Info formatting programs, such as `texin
`makeinfo'.
If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-6.3', in the case of version 6.3), you can make
+source directory (`gdb-6.6.90', in the case of version 6.6.90), you can make
the Info file by typing:
cd gdb/doc
@@ -134,7 +134,7 @@ the Info file by typing:
If you want to typeset and print copies of this manual, you need
TeX, a program to print its DVI output files, and `texinfo.tex', the
Texinfo definitions file. This file is included in the GDB
-distribution, in the directory `gdb-6.3/texinfo'.
+distribution, in the directory `gdb-6.6.90/texinfo'.
TeX is a typesetting program; it does not print files directly, but
produces output files called DVI files. To print a typeset document,
@@ -148,11 +148,11 @@ without any extension or a `.dvi' extens
This file tells TeX how to typeset a document written in Texinfo
format. On its own, TeX cannot read, much less typeset a Texinfo file.
`texinfo.tex' is distributed with GDB and is located in the
-`gdb-6.3/texinfo' directory.
+`gdb-6.6.90/texinfo' directory.
If you have TeX and a DVI printer program installed, you can typeset
and print this manual. First switch to the the `gdb' subdirectory of
-the main source directory (for example, to `gdb-6.3/gdb') and then type:
+the main source directory (for example, to `gdb-6.6.90/gdb') and then type:
make doc/gdb.dvi
@@ -175,43 +175,43 @@ preparing GDB for installation; you can
a single directory, whose name is usually composed by appending the
version number to `gdb'.
- For example, the GDB version 6.3 distribution is in the `gdb-6.3'
+ For example, the GDB version 6.6.90 distribution is in the `gdb-6.6.90'
directory. That directory contains:
-`gdb-6.3/{COPYING,COPYING.LIB}'
+`gdb-6.6.90/{COPYING,COPYING.LIB}'
Standard GNU license files. Please read them.
-`gdb-6.3/bfd'
+`gdb-6.6.90/bfd'
source for the Binary File Descriptor library
-`gdb-6.3/config*'
+`gdb-6.6.90/config*'
script for configuring GDB, along with other support files
-`gdb-6.3/gdb'
+`gdb-6.6.90/gdb'
the source specific to GDB itself
-`gdb-6.3/include'
+`gdb-6.6.90/include'
GNU include files
-`gdb-6.3/libiberty'
+`gdb-6.6.90/libiberty'
source for the `-liberty' free software library
-`gdb-6.3/opcodes'
+`gdb-6.6.90/opcodes'
source for the library of opcode tables and disassemblers
-`gdb-6.3/readline'
+`gdb-6.6.90/readline'
source for the GNU command-line interface
NOTE: The readline library is compiled for use by GDB, but will
not be installed on your system when "make install" is issued.
-`gdb-6.3/sim'
+`gdb-6.6.90/sim'
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
-`gdb-6.3/texinfo'
+`gdb-6.6.90/texinfo'
The `texinfo.tex' file, which you need in order to make a printed
manual using TeX.
-`gdb-6.3/etc'
+`gdb-6.6.90/etc'
Coding standards, useful files for editing GDB, and other
miscellanea.
@@ -221,14 +221,14 @@ MS-DOS/MS-Windows are in the file gdb/co
The simplest way to configure and build GDB is to run `configure'
from the `gdb-VERSION-NUMBER' source directory, which in this example
-is the `gdb-6.3' directory.
+is the `gdb-6.6.90' directory.
First switch to the `gdb-VERSION-NUMBER' source directory if you are
not already in it; then run `configure'.
For example:
- cd gdb-6.3
+ cd gdb-6.6.90
./configure
make
@@ -244,8 +244,8 @@ you may need to run `sh' on it explicitl
sh configure
If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-6.3'
-source directory for version 6.3, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-6.6.90'
+source directory for version 6.6.90, `configure' creates configuration
files for every directory level underneath (unless you tell it not to,
with the `--norecursion' option).
@@ -253,10 +253,10 @@ with the `--norecursion' option).
directories in the GDB distribution, if you only want to configure that
subdirectory; but be sure to specify a path to it.
- For example, with version 6.3, type the following to configure only
+ For example, with version 6.6.90, type the following to configure only
the `bfd' subdirectory:
- cd gdb-6.3/bfd
+ cd gdb-6.6.90/bfd
../configure
You can install `gdb' anywhere; it has no hardwired paths. However,
@@ -285,13 +285,13 @@ directory. If the path to `configure' w
argument to `--srcdir', you can leave out the `--srcdir' option; it
will be assumed.)
- For example, with version 6.3, you can build GDB in a separate
+ For example, with version 6.6.90, you can build GDB in a separate
directory for a Sun 4 like this:
- cd gdb-6.3
+ cd gdb-6.6.90
mkdir ../gdb-sun4
cd ../gdb-sun4
- ../gdb-6.3/configure
+ ../gdb-6.6.90/configure
make
When `configure' builds a configuration using a remote source
@@ -312,8 +312,8 @@ called `configure' (or one of its subdir
The `Makefile' that `configure' generates in each source directory
also runs recursively. If you type `make' in a source directory such
-as `gdb-6.3' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-6.3'), you will build all the required libraries,
+as `gdb-6.6.90' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-6.6.90'), you will build all the required libraries,
and then build GDB.
When you have multiple hosts or targets configured in separate
@@ -356,7 +356,7 @@ you can use it to test your guesses on a
Invalid configuration `i786v': machine `i786v' not recognized
`config.sub' is also distributed in the GDB source directory
-(`gdb-6.3', for version 6.3).
+(`gdb-6.6.90', for version 6.6.90).
`configure' options
@@ -474,7 +474,7 @@ As an alternative, the bug report can be
address "bug-gdb@gnu.org".
When submitting a bug, please include the GDB version number (e.g.,
-gdb-6.3), and how you configured it (e.g., "sun4" or "mach386 host,
+gdb-6.6.90), and how you configured it (e.g., "sun4" or "mach386 host,
i586-intel-synopsys target"). Since GDB now supports so many
different configurations, it is important that you be precise about
this. If at all possible, you should include the actual banner that
@@ -529,17 +529,17 @@ ftp://sources.redhat.com/pub/dejagnu/ wi
Once DejaGNU is installed, you can run the tests in one of the
following ways:
- (1) cd gdb-6.3
+ (1) cd gdb-6.6.90
make check-gdb
or
- (2) cd gdb-6.3/gdb
+ (2) cd gdb-6.6.90/gdb
make check
or
- (3) cd gdb-6.3/gdb/testsuite
+ (3) cd gdb-6.6.90/gdb/testsuite
make site.exp (builds the site specific file)
runtest -tool gdb GDB=../gdb (or GDB=<somepath> as appropriate)
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.8684.2.3
diff -u -p -r1.8684.2.3 ChangeLog
--- ChangeLog 19 Sep 2007 14:46:28 -0000 1.8684.2.3
+++ ChangeLog 19 Sep 2007 19:47:23 -0000
@@ -1,3 +1,7 @@
+2007-09-19 Joel Brobecker <brobecker@adacore.com>
+
+ * README: Update GDB version number to 6.6.90.
+
2007-09-19 Daniel Jacobowitz <dan@codesourcery.com>
* mips-tdep.c (mips_stub_frame_cache): Correct the saved return
^ permalink raw reply [flat|nested] 7+ messages in thread* [commit/branch] Update GDB version in README
@ 2008-03-13 17:42 Joel Brobecker
0 siblings, 0 replies; 7+ messages in thread
From: Joel Brobecker @ 2008-03-13 17:42 UTC (permalink / raw)
To: gdb-patches
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
Hello,
In preparation for the upcoming GDB 6.7.90 pre-release, I have
adjusted the version number in the README file.
2008-03-13 Joel Brobecker <brobecker@adacore.com>
* README: Update GDB version number to 6.7.90.
--
Joel
[-- Attachment #2: readme_version.diff --]
[-- Type: text/plain, Size: 11283 bytes --]
Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.42
diff -u -p -r1.42 README
--- README 17 Jan 2008 20:18:48 -0000 1.42
+++ README 13 Mar 2008 17:39:32 -0000
@@ -1,5 +1,5 @@
- README for gdb-6.3 release
- Updated 20, November, 2006
+ README for gdb-6.7.90 release
+ Updated 13, March, 2008
This is GDB, the GNU source-level debugger.
@@ -20,7 +20,7 @@ Unpacking and Installation -- quick over
In this release, the GDB debugger sources, the generic GNU include
files, the BFD ("binary file description") library, the readline
library, and other libraries all have directories of their own
-underneath the gdb-6.3 directory. The idea is that a variety of GNU
+underneath the gdb-6.7.90 directory. The idea is that a variety of GNU
tools can share a common copy of these things. Be aware of variation
over time--for example don't try to build gdb with a copy of bfd from
a release other than the gdb release (such as a binutils release),
@@ -29,8 +29,8 @@ Configuration scripts and makefiles exis
directory tree and automatically build all the pieces in the right
order.
- When you unpack the gdb-6.3.tar.gz file, you'll find a directory
-called `gdb-6.3', which contains:
+ When you unpack the gdb-6.7.90.tar.gz file, you'll find a directory
+called `gdb-6.7.90', which contains:
COPYING config-ml.in gettext.m4 ltconfig sim
COPYING.LIB config.guess include ltmain.sh src-release
@@ -43,7 +43,7 @@ called `gdb-6.3', which contains:
You can build GDB right in the source directory:
- cd gdb-6.3
+ cd gdb-6.7.90
./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
@@ -57,25 +57,25 @@ You can build GDB in any empty build dir
mkdir build
cd build
- <full path to your sources>/gdb-6.3/configure
+ <full path to your sources>/gdb-6.7.90/configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
-different; see the file gdb-6.3/gdb/config/djgpp/README for details.)
+different; see the file gdb-6.7.90/gdb/config/djgpp/README for details.)
This will configure and build all the libraries as well as GDB. If
`configure' can't determine your system type, specify one as its
argument, e.g., `./configure sun4' or `./configure decstation'.
- Make sure that your 'configure' line ends in 'gdb-6.3/configure':
+ Make sure that your 'configure' line ends in 'gdb-6.7.90/configure':
- /berman/migchain/source/gdb-6.3/configure # RIGHT
- /berman/migchain/source/gdb-6.3/gdb/configure # WRONG
+ /berman/migchain/source/gdb-6.7.90/configure # RIGHT
+ /berman/migchain/source/gdb-6.7.90/gdb/configure # WRONG
The gdb package contains several subdirectories, such as 'gdb',
'bfd', and 'readline'. If your 'configure' line ends in
-'gdb-6.3/gdb/configure', then you are configuring only the gdb
+'gdb-6.7.90/gdb/configure', then you are configuring only the gdb
subdirectory, not the whole gdb package. This leads to build errors
such as:
@@ -113,7 +113,7 @@ documentation and TeX (or `texi2roff') t
GDB includes an already formatted copy of the on-line Info version
of this manual in the `gdb/doc' subdirectory. The main Info file is
-`gdb-6.3/gdb/doc/gdb.info', and it refers to subordinate files
+`gdb-6.7.90/gdb/doc/gdb.info', and it refers to subordinate files
matching `gdb.info*' in the same directory. If necessary, you can
print out these files, or read them with any editor; but they are
easier to read using the `info' subsystem in GNU Emacs or the
@@ -125,7 +125,7 @@ Info formatting programs, such as `texin
`makeinfo'.
If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-6.3', in the case of version 6.3), you can make
+source directory (`gdb-6.7.90', in the case of version 6.7.90), you can make
the Info file by typing:
cd gdb/doc
@@ -134,7 +134,7 @@ the Info file by typing:
If you want to typeset and print copies of this manual, you need
TeX, a program to print its DVI output files, and `texinfo.tex', the
Texinfo definitions file. This file is included in the GDB
-distribution, in the directory `gdb-6.3/texinfo'.
+distribution, in the directory `gdb-6.7.90/texinfo'.
TeX is a typesetting program; it does not print files directly, but
produces output files called DVI files. To print a typeset document,
@@ -148,11 +148,11 @@ without any extension or a `.dvi' extens
This file tells TeX how to typeset a document written in Texinfo
format. On its own, TeX cannot read, much less typeset a Texinfo file.
`texinfo.tex' is distributed with GDB and is located in the
-`gdb-6.3/texinfo' directory.
+`gdb-6.7.90/texinfo' directory.
If you have TeX and a DVI printer program installed, you can typeset
and print this manual. First switch to the the `gdb' subdirectory of
-the main source directory (for example, to `gdb-6.3/gdb') and then type:
+the main source directory (for example, to `gdb-6.7.90/gdb') and then type:
make doc/gdb.dvi
@@ -175,43 +175,43 @@ preparing GDB for installation; you can
a single directory, whose name is usually composed by appending the
version number to `gdb'.
- For example, the GDB version 6.3 distribution is in the `gdb-6.3'
+ For example, the GDB version 6.7.90 distribution is in the `gdb-6.7.90'
directory. That directory contains:
-`gdb-6.3/{COPYING,COPYING.LIB}'
+`gdb-6.7.90/{COPYING,COPYING.LIB}'
Standard GNU license files. Please read them.
-`gdb-6.3/bfd'
+`gdb-6.7.90/bfd'
source for the Binary File Descriptor library
-`gdb-6.3/config*'
+`gdb-6.7.90/config*'
script for configuring GDB, along with other support files
-`gdb-6.3/gdb'
+`gdb-6.7.90/gdb'
the source specific to GDB itself
-`gdb-6.3/include'
+`gdb-6.7.90/include'
GNU include files
-`gdb-6.3/libiberty'
+`gdb-6.7.90/libiberty'
source for the `-liberty' free software library
-`gdb-6.3/opcodes'
+`gdb-6.7.90/opcodes'
source for the library of opcode tables and disassemblers
-`gdb-6.3/readline'
+`gdb-6.7.90/readline'
source for the GNU command-line interface
NOTE: The readline library is compiled for use by GDB, but will
not be installed on your system when "make install" is issued.
-`gdb-6.3/sim'
+`gdb-6.7.90/sim'
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
-`gdb-6.3/texinfo'
+`gdb-6.7.90/texinfo'
The `texinfo.tex' file, which you need in order to make a printed
manual using TeX.
-`gdb-6.3/etc'
+`gdb-6.7.90/etc'
Coding standards, useful files for editing GDB, and other
miscellanea.
@@ -221,14 +221,14 @@ MS-DOS/MS-Windows are in the file gdb/co
The simplest way to configure and build GDB is to run `configure'
from the `gdb-VERSION-NUMBER' source directory, which in this example
-is the `gdb-6.3' directory.
+is the `gdb-6.7.90' directory.
First switch to the `gdb-VERSION-NUMBER' source directory if you are
not already in it; then run `configure'.
For example:
- cd gdb-6.3
+ cd gdb-6.7.90
./configure
make
@@ -244,8 +244,8 @@ you may need to run `sh' on it explicitl
sh configure
If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-6.3'
-source directory for version 6.3, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-6.7.90'
+source directory for version 6.7.90, `configure' creates configuration
files for every directory level underneath (unless you tell it not to,
with the `--norecursion' option).
@@ -253,10 +253,10 @@ with the `--norecursion' option).
directories in the GDB distribution, if you only want to configure that
subdirectory; but be sure to specify a path to it.
- For example, with version 6.3, type the following to configure only
+ For example, with version 6.7.90, type the following to configure only
the `bfd' subdirectory:
- cd gdb-6.3/bfd
+ cd gdb-6.7.90/bfd
../configure
You can install `gdb' anywhere; it has no hardwired paths. However,
@@ -285,13 +285,13 @@ directory. If the path to `configure' w
argument to `--srcdir', you can leave out the `--srcdir' option; it
will be assumed.)
- For example, with version 6.3, you can build GDB in a separate
+ For example, with version 6.7.90, you can build GDB in a separate
directory for a Sun 4 like this:
- cd gdb-6.3
+ cd gdb-6.7.90
mkdir ../gdb-sun4
cd ../gdb-sun4
- ../gdb-6.3/configure
+ ../gdb-6.7.90/configure
make
When `configure' builds a configuration using a remote source
@@ -312,8 +312,8 @@ called `configure' (or one of its subdir
The `Makefile' that `configure' generates in each source directory
also runs recursively. If you type `make' in a source directory such
-as `gdb-6.3' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-6.3'), you will build all the required libraries,
+as `gdb-6.7.90' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-6.7.90'), you will build all the required libraries,
and then build GDB.
When you have multiple hosts or targets configured in separate
@@ -356,7 +356,7 @@ you can use it to test your guesses on a
Invalid configuration `i786v': machine `i786v' not recognized
`config.sub' is also distributed in the GDB source directory
-(`gdb-6.3', for version 6.3).
+(`gdb-6.7.90', for version 6.7.90).
`configure' options
@@ -478,7 +478,7 @@ As an alternative, the bug report can be
address "bug-gdb@gnu.org".
When submitting a bug, please include the GDB version number (e.g.,
-gdb-6.3), and how you configured it (e.g., "sun4" or "mach386 host,
+gdb-6.7.90), and how you configured it (e.g., "sun4" or "mach386 host,
i586-intel-synopsys target"). Since GDB now supports so many
different configurations, it is important that you be precise about
this. If at all possible, you should include the actual banner that
@@ -533,17 +533,17 @@ ftp://sources.redhat.com/pub/dejagnu/ wi
Once DejaGNU is installed, you can run the tests in one of the
following ways:
- (1) cd gdb-6.3
+ (1) cd gdb-6.7.90
make check-gdb
or
- (2) cd gdb-6.3/gdb
+ (2) cd gdb-6.7.90/gdb
make check
or
- (3) cd gdb-6.3/gdb/testsuite
+ (3) cd gdb-6.7.90/gdb/testsuite
make site.exp (builds the site specific file)
runtest -tool gdb GDB=../gdb (or GDB=<somepath> as appropriate)
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.9174.2.8
diff -u -p -r1.9174.2.8 ChangeLog
--- ChangeLog 12 Mar 2008 22:27:46 -0000 1.9174.2.8
+++ ChangeLog 13 Mar 2008 17:39:32 -0000
@@ -1,3 +1,7 @@
+2008-03-13 Joel Brobecker <brobecker@adacore.com>
+
+ * README: Update GDB version number to 6.7.90.
+
2008-03-12 Pedro Alves <pedro@codesourcery.com>
* thread.c (add_thread): Use printf_unfiltered to print.
^ permalink raw reply [flat|nested] 7+ messages in thread* [commit/branch] Update GDB version in README
@ 2007-10-29 17:55 Joel Brobecker
0 siblings, 0 replies; 7+ messages in thread
From: Joel Brobecker @ 2007-10-29 17:55 UTC (permalink / raw)
To: gdb-patches
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
Hello,
In preparation for the upcoming GDB 6.7.1 release, I have
adjusted the version number in the README file.
2007-10-29 Joel Brobecker <brobecker@adacore.com>
* README: Update GDB version number to 6.7.1.
--
Joel
PS: I am realizing now that I could be more efficient and bunch
this change will several other changes I am about to make.
Right now, I'm just following my procedure with my scripts,
but will try to improve the scripts for 6.8/7.0.
[-- Attachment #2: readme_version.diff --]
[-- Type: text/plain, Size: 11260 bytes --]
Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.41.2.2
diff -u -p -r1.41.2.2 README
--- README 10 Oct 2007 17:03:10 -0000 1.41.2.2
+++ README 29 Oct 2007 17:44:02 -0000
@@ -1,5 +1,5 @@
- README for gdb-6.7 release
- Updated 10, October, 2007
+ README for gdb-6.7.1 release
+ Updated 29, October, 2007
This is GDB, the GNU source-level debugger.
@@ -20,7 +20,7 @@ Unpacking and Installation -- quick over
In this release, the GDB debugger sources, the generic GNU include
files, the BFD ("binary file description") library, the readline
library, and other libraries all have directories of their own
-underneath the gdb-6.7 directory. The idea is that a variety of GNU
+underneath the gdb-6.7.1 directory. The idea is that a variety of GNU
tools can share a common copy of these things. Be aware of variation
over time--for example don't try to build gdb with a copy of bfd from
a release other than the gdb release (such as a binutils release),
@@ -29,8 +29,8 @@ Configuration scripts and makefiles exis
directory tree and automatically build all the pieces in the right
order.
- When you unpack the gdb-6.7.tar.gz file, you'll find a directory
-called `gdb-6.7', which contains:
+ When you unpack the gdb-6.7.1.tar.gz file, you'll find a directory
+called `gdb-6.7.1', which contains:
COPYING config-ml.in gettext.m4 ltconfig sim
COPYING.LIB config.guess include ltmain.sh src-release
@@ -43,7 +43,7 @@ called `gdb-6.7', which contains:
You can build GDB right in the source directory:
- cd gdb-6.7
+ cd gdb-6.7.1
./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
@@ -57,25 +57,25 @@ You can build GDB in any empty build dir
mkdir build
cd build
- <full path to your sources>/gdb-6.7/configure
+ <full path to your sources>/gdb-6.7.1/configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
-different; see the file gdb-6.7/gdb/config/djgpp/README for details.)
+different; see the file gdb-6.7.1/gdb/config/djgpp/README for details.)
This will configure and build all the libraries as well as GDB. If
`configure' can't determine your system type, specify one as its
argument, e.g., `./configure sun4' or `./configure decstation'.
- Make sure that your 'configure' line ends in 'gdb-6.7/configure':
+ Make sure that your 'configure' line ends in 'gdb-6.7.1/configure':
- /berman/migchain/source/gdb-6.7/configure # RIGHT
- /berman/migchain/source/gdb-6.7/gdb/configure # WRONG
+ /berman/migchain/source/gdb-6.7.1/configure # RIGHT
+ /berman/migchain/source/gdb-6.7.1/gdb/configure # WRONG
The gdb package contains several subdirectories, such as 'gdb',
'bfd', and 'readline'. If your 'configure' line ends in
-'gdb-6.7/gdb/configure', then you are configuring only the gdb
+'gdb-6.7.1/gdb/configure', then you are configuring only the gdb
subdirectory, not the whole gdb package. This leads to build errors
such as:
@@ -113,7 +113,7 @@ documentation and TeX (or `texi2roff') t
GDB includes an already formatted copy of the on-line Info version
of this manual in the `gdb/doc' subdirectory. The main Info file is
-`gdb-6.7/gdb/doc/gdb.info', and it refers to subordinate files
+`gdb-6.7.1/gdb/doc/gdb.info', and it refers to subordinate files
matching `gdb.info*' in the same directory. If necessary, you can
print out these files, or read them with any editor; but they are
easier to read using the `info' subsystem in GNU Emacs or the
@@ -125,7 +125,7 @@ Info formatting programs, such as `texin
`makeinfo'.
If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-6.7', in the case of version 6.7), you can make
+source directory (`gdb-6.7.1', in the case of version 6.7.1), you can make
the Info file by typing:
cd gdb/doc
@@ -134,7 +134,7 @@ the Info file by typing:
If you want to typeset and print copies of this manual, you need
TeX, a program to print its DVI output files, and `texinfo.tex', the
Texinfo definitions file. This file is included in the GDB
-distribution, in the directory `gdb-6.7/texinfo'.
+distribution, in the directory `gdb-6.7.1/texinfo'.
TeX is a typesetting program; it does not print files directly, but
produces output files called DVI files. To print a typeset document,
@@ -148,11 +148,11 @@ without any extension or a `.dvi' extens
This file tells TeX how to typeset a document written in Texinfo
format. On its own, TeX cannot read, much less typeset a Texinfo file.
`texinfo.tex' is distributed with GDB and is located in the
-`gdb-6.7/texinfo' directory.
+`gdb-6.7.1/texinfo' directory.
If you have TeX and a DVI printer program installed, you can typeset
and print this manual. First switch to the the `gdb' subdirectory of
-the main source directory (for example, to `gdb-6.7/gdb') and then type:
+the main source directory (for example, to `gdb-6.7.1/gdb') and then type:
make doc/gdb.dvi
@@ -175,43 +175,43 @@ preparing GDB for installation; you can
a single directory, whose name is usually composed by appending the
version number to `gdb'.
- For example, the GDB version 6.7 distribution is in the `gdb-6.7'
+ For example, the GDB version 6.7.1 distribution is in the `gdb-6.7.1'
directory. That directory contains:
-`gdb-6.7/{COPYING,COPYING.LIB}'
+`gdb-6.7.1/{COPYING,COPYING.LIB}'
Standard GNU license files. Please read them.
-`gdb-6.7/bfd'
+`gdb-6.7.1/bfd'
source for the Binary File Descriptor library
-`gdb-6.7/config*'
+`gdb-6.7.1/config*'
script for configuring GDB, along with other support files
-`gdb-6.7/gdb'
+`gdb-6.7.1/gdb'
the source specific to GDB itself
-`gdb-6.7/include'
+`gdb-6.7.1/include'
GNU include files
-`gdb-6.7/libiberty'
+`gdb-6.7.1/libiberty'
source for the `-liberty' free software library
-`gdb-6.7/opcodes'
+`gdb-6.7.1/opcodes'
source for the library of opcode tables and disassemblers
-`gdb-6.7/readline'
+`gdb-6.7.1/readline'
source for the GNU command-line interface
NOTE: The readline library is compiled for use by GDB, but will
not be installed on your system when "make install" is issued.
-`gdb-6.7/sim'
+`gdb-6.7.1/sim'
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
-`gdb-6.7/texinfo'
+`gdb-6.7.1/texinfo'
The `texinfo.tex' file, which you need in order to make a printed
manual using TeX.
-`gdb-6.7/etc'
+`gdb-6.7.1/etc'
Coding standards, useful files for editing GDB, and other
miscellanea.
@@ -221,14 +221,14 @@ MS-DOS/MS-Windows are in the file gdb/co
The simplest way to configure and build GDB is to run `configure'
from the `gdb-VERSION-NUMBER' source directory, which in this example
-is the `gdb-6.7' directory.
+is the `gdb-6.7.1' directory.
First switch to the `gdb-VERSION-NUMBER' source directory if you are
not already in it; then run `configure'.
For example:
- cd gdb-6.7
+ cd gdb-6.7.1
./configure
make
@@ -244,8 +244,8 @@ you may need to run `sh' on it explicitl
sh configure
If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-6.7'
-source directory for version 6.7, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-6.7.1'
+source directory for version 6.7.1, `configure' creates configuration
files for every directory level underneath (unless you tell it not to,
with the `--norecursion' option).
@@ -253,10 +253,10 @@ with the `--norecursion' option).
directories in the GDB distribution, if you only want to configure that
subdirectory; but be sure to specify a path to it.
- For example, with version 6.7, type the following to configure only
+ For example, with version 6.7.1, type the following to configure only
the `bfd' subdirectory:
- cd gdb-6.7/bfd
+ cd gdb-6.7.1/bfd
../configure
You can install `gdb' anywhere; it has no hardwired paths. However,
@@ -285,13 +285,13 @@ directory. If the path to `configure' w
argument to `--srcdir', you can leave out the `--srcdir' option; it
will be assumed.)
- For example, with version 6.7, you can build GDB in a separate
+ For example, with version 6.7.1, you can build GDB in a separate
directory for a Sun 4 like this:
- cd gdb-6.7
+ cd gdb-6.7.1
mkdir ../gdb-sun4
cd ../gdb-sun4
- ../gdb-6.7/configure
+ ../gdb-6.7.1/configure
make
When `configure' builds a configuration using a remote source
@@ -312,8 +312,8 @@ called `configure' (or one of its subdir
The `Makefile' that `configure' generates in each source directory
also runs recursively. If you type `make' in a source directory such
-as `gdb-6.7' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-6.7'), you will build all the required libraries,
+as `gdb-6.7.1' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-6.7.1'), you will build all the required libraries,
and then build GDB.
When you have multiple hosts or targets configured in separate
@@ -356,7 +356,7 @@ you can use it to test your guesses on a
Invalid configuration `i786v': machine `i786v' not recognized
`config.sub' is also distributed in the GDB source directory
-(`gdb-6.7', for version 6.7).
+(`gdb-6.7.1', for version 6.7.1).
`configure' options
@@ -474,7 +474,7 @@ As an alternative, the bug report can be
address "bug-gdb@gnu.org".
When submitting a bug, please include the GDB version number (e.g.,
-gdb-6.7), and how you configured it (e.g., "sun4" or "mach386 host,
+gdb-6.7.1), and how you configured it (e.g., "sun4" or "mach386 host,
i586-intel-synopsys target"). Since GDB now supports so many
different configurations, it is important that you be precise about
this. If at all possible, you should include the actual banner that
@@ -529,17 +529,17 @@ ftp://sources.redhat.com/pub/dejagnu/ wi
Once DejaGNU is installed, you can run the tests in one of the
following ways:
- (1) cd gdb-6.7
+ (1) cd gdb-6.7.1
make check-gdb
or
- (2) cd gdb-6.7/gdb
+ (2) cd gdb-6.7.1/gdb
make check
or
- (3) cd gdb-6.7/gdb/testsuite
+ (3) cd gdb-6.7.1/gdb/testsuite
make site.exp (builds the site specific file)
runtest -tool gdb GDB=../gdb (or GDB=<somepath> as appropriate)
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.8684.2.28
diff -u -p -r1.8684.2.28 ChangeLog
--- ChangeLog 25 Oct 2007 21:40:55 -0000 1.8684.2.28
+++ ChangeLog 29 Oct 2007 17:44:02 -0000
@@ -1,3 +1,7 @@
+2007-10-29 Joel Brobecker <brobecker@adacore.com>
+
+ * README: Update GDB version number to 6.7.1.
+
2007-10-25 Pedro Alves <pedro_alves@portugalmail.pt>
* memory-map.c (parse_memory_map): Don't use an empty struct
^ permalink raw reply [flat|nested] 7+ messages in thread* [commit/branch] Update GDB version in README
@ 2007-10-10 17:20 Joel Brobecker
0 siblings, 0 replies; 7+ messages in thread
From: Joel Brobecker @ 2007-10-10 17:20 UTC (permalink / raw)
To: gdb-patches
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
Hello,
In preparation for the upcoming GDB 6.7 release, I have
adjusted the version number in the README file.
2007-10-10 Joel Brobecker <brobecker@adacore.com>
* README: Update GDB version number to 6.7.
--
Joel
[-- Attachment #2: readme_version.diff --]
[-- Type: text/plain, Size: 11309 bytes --]
Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.41.2.1
diff -u -p -r1.41.2.1 README
--- README 19 Sep 2007 19:47:54 -0000 1.41.2.1
+++ README 10 Oct 2007 17:02:54 -0000
@@ -1,5 +1,5 @@
- README for gdb-6.6.90 release
- Updated 19, September, 2007
+ README for gdb-6.7 release
+ Updated 10, October, 2007
This is GDB, the GNU source-level debugger.
@@ -20,7 +20,7 @@ Unpacking and Installation -- quick over
In this release, the GDB debugger sources, the generic GNU include
files, the BFD ("binary file description") library, the readline
library, and other libraries all have directories of their own
-underneath the gdb-6.6.90 directory. The idea is that a variety of GNU
+underneath the gdb-6.7 directory. The idea is that a variety of GNU
tools can share a common copy of these things. Be aware of variation
over time--for example don't try to build gdb with a copy of bfd from
a release other than the gdb release (such as a binutils release),
@@ -29,8 +29,8 @@ Configuration scripts and makefiles exis
directory tree and automatically build all the pieces in the right
order.
- When you unpack the gdb-6.6.90.tar.gz file, you'll find a directory
-called `gdb-6.6.90', which contains:
+ When you unpack the gdb-6.7.tar.gz file, you'll find a directory
+called `gdb-6.7', which contains:
COPYING config-ml.in gettext.m4 ltconfig sim
COPYING.LIB config.guess include ltmain.sh src-release
@@ -43,7 +43,7 @@ called `gdb-6.6.90', which contains:
You can build GDB right in the source directory:
- cd gdb-6.6.90
+ cd gdb-6.7
./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
@@ -57,25 +57,25 @@ You can build GDB in any empty build dir
mkdir build
cd build
- <full path to your sources>/gdb-6.6.90/configure
+ <full path to your sources>/gdb-6.7/configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
-different; see the file gdb-6.6.90/gdb/config/djgpp/README for details.)
+different; see the file gdb-6.7/gdb/config/djgpp/README for details.)
This will configure and build all the libraries as well as GDB. If
`configure' can't determine your system type, specify one as its
argument, e.g., `./configure sun4' or `./configure decstation'.
- Make sure that your 'configure' line ends in 'gdb-6.6.90/configure':
+ Make sure that your 'configure' line ends in 'gdb-6.7/configure':
- /berman/migchain/source/gdb-6.6.90/configure # RIGHT
- /berman/migchain/source/gdb-6.6.90/gdb/configure # WRONG
+ /berman/migchain/source/gdb-6.7/configure # RIGHT
+ /berman/migchain/source/gdb-6.7/gdb/configure # WRONG
The gdb package contains several subdirectories, such as 'gdb',
'bfd', and 'readline'. If your 'configure' line ends in
-'gdb-6.6.90/gdb/configure', then you are configuring only the gdb
+'gdb-6.7/gdb/configure', then you are configuring only the gdb
subdirectory, not the whole gdb package. This leads to build errors
such as:
@@ -113,7 +113,7 @@ documentation and TeX (or `texi2roff') t
GDB includes an already formatted copy of the on-line Info version
of this manual in the `gdb/doc' subdirectory. The main Info file is
-`gdb-6.6.90/gdb/doc/gdb.info', and it refers to subordinate files
+`gdb-6.7/gdb/doc/gdb.info', and it refers to subordinate files
matching `gdb.info*' in the same directory. If necessary, you can
print out these files, or read them with any editor; but they are
easier to read using the `info' subsystem in GNU Emacs or the
@@ -125,7 +125,7 @@ Info formatting programs, such as `texin
`makeinfo'.
If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-6.6.90', in the case of version 6.6.90), you can make
+source directory (`gdb-6.7', in the case of version 6.7), you can make
the Info file by typing:
cd gdb/doc
@@ -134,7 +134,7 @@ the Info file by typing:
If you want to typeset and print copies of this manual, you need
TeX, a program to print its DVI output files, and `texinfo.tex', the
Texinfo definitions file. This file is included in the GDB
-distribution, in the directory `gdb-6.6.90/texinfo'.
+distribution, in the directory `gdb-6.7/texinfo'.
TeX is a typesetting program; it does not print files directly, but
produces output files called DVI files. To print a typeset document,
@@ -148,11 +148,11 @@ without any extension or a `.dvi' extens
This file tells TeX how to typeset a document written in Texinfo
format. On its own, TeX cannot read, much less typeset a Texinfo file.
`texinfo.tex' is distributed with GDB and is located in the
-`gdb-6.6.90/texinfo' directory.
+`gdb-6.7/texinfo' directory.
If you have TeX and a DVI printer program installed, you can typeset
and print this manual. First switch to the the `gdb' subdirectory of
-the main source directory (for example, to `gdb-6.6.90/gdb') and then type:
+the main source directory (for example, to `gdb-6.7/gdb') and then type:
make doc/gdb.dvi
@@ -175,43 +175,43 @@ preparing GDB for installation; you can
a single directory, whose name is usually composed by appending the
version number to `gdb'.
- For example, the GDB version 6.6.90 distribution is in the `gdb-6.6.90'
+ For example, the GDB version 6.7 distribution is in the `gdb-6.7'
directory. That directory contains:
-`gdb-6.6.90/{COPYING,COPYING.LIB}'
+`gdb-6.7/{COPYING,COPYING.LIB}'
Standard GNU license files. Please read them.
-`gdb-6.6.90/bfd'
+`gdb-6.7/bfd'
source for the Binary File Descriptor library
-`gdb-6.6.90/config*'
+`gdb-6.7/config*'
script for configuring GDB, along with other support files
-`gdb-6.6.90/gdb'
+`gdb-6.7/gdb'
the source specific to GDB itself
-`gdb-6.6.90/include'
+`gdb-6.7/include'
GNU include files
-`gdb-6.6.90/libiberty'
+`gdb-6.7/libiberty'
source for the `-liberty' free software library
-`gdb-6.6.90/opcodes'
+`gdb-6.7/opcodes'
source for the library of opcode tables and disassemblers
-`gdb-6.6.90/readline'
+`gdb-6.7/readline'
source for the GNU command-line interface
NOTE: The readline library is compiled for use by GDB, but will
not be installed on your system when "make install" is issued.
-`gdb-6.6.90/sim'
+`gdb-6.7/sim'
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
-`gdb-6.6.90/texinfo'
+`gdb-6.7/texinfo'
The `texinfo.tex' file, which you need in order to make a printed
manual using TeX.
-`gdb-6.6.90/etc'
+`gdb-6.7/etc'
Coding standards, useful files for editing GDB, and other
miscellanea.
@@ -221,14 +221,14 @@ MS-DOS/MS-Windows are in the file gdb/co
The simplest way to configure and build GDB is to run `configure'
from the `gdb-VERSION-NUMBER' source directory, which in this example
-is the `gdb-6.6.90' directory.
+is the `gdb-6.7' directory.
First switch to the `gdb-VERSION-NUMBER' source directory if you are
not already in it; then run `configure'.
For example:
- cd gdb-6.6.90
+ cd gdb-6.7
./configure
make
@@ -244,8 +244,8 @@ you may need to run `sh' on it explicitl
sh configure
If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-6.6.90'
-source directory for version 6.6.90, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-6.7'
+source directory for version 6.7, `configure' creates configuration
files for every directory level underneath (unless you tell it not to,
with the `--norecursion' option).
@@ -253,10 +253,10 @@ with the `--norecursion' option).
directories in the GDB distribution, if you only want to configure that
subdirectory; but be sure to specify a path to it.
- For example, with version 6.6.90, type the following to configure only
+ For example, with version 6.7, type the following to configure only
the `bfd' subdirectory:
- cd gdb-6.6.90/bfd
+ cd gdb-6.7/bfd
../configure
You can install `gdb' anywhere; it has no hardwired paths. However,
@@ -285,13 +285,13 @@ directory. If the path to `configure' w
argument to `--srcdir', you can leave out the `--srcdir' option; it
will be assumed.)
- For example, with version 6.6.90, you can build GDB in a separate
+ For example, with version 6.7, you can build GDB in a separate
directory for a Sun 4 like this:
- cd gdb-6.6.90
+ cd gdb-6.7
mkdir ../gdb-sun4
cd ../gdb-sun4
- ../gdb-6.6.90/configure
+ ../gdb-6.7/configure
make
When `configure' builds a configuration using a remote source
@@ -312,8 +312,8 @@ called `configure' (or one of its subdir
The `Makefile' that `configure' generates in each source directory
also runs recursively. If you type `make' in a source directory such
-as `gdb-6.6.90' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-6.6.90'), you will build all the required libraries,
+as `gdb-6.7' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-6.7'), you will build all the required libraries,
and then build GDB.
When you have multiple hosts or targets configured in separate
@@ -356,7 +356,7 @@ you can use it to test your guesses on a
Invalid configuration `i786v': machine `i786v' not recognized
`config.sub' is also distributed in the GDB source directory
-(`gdb-6.6.90', for version 6.6.90).
+(`gdb-6.7', for version 6.7).
`configure' options
@@ -474,7 +474,7 @@ As an alternative, the bug report can be
address "bug-gdb@gnu.org".
When submitting a bug, please include the GDB version number (e.g.,
-gdb-6.6.90), and how you configured it (e.g., "sun4" or "mach386 host,
+gdb-6.7), and how you configured it (e.g., "sun4" or "mach386 host,
i586-intel-synopsys target"). Since GDB now supports so many
different configurations, it is important that you be precise about
this. If at all possible, you should include the actual banner that
@@ -529,17 +529,17 @@ ftp://sources.redhat.com/pub/dejagnu/ wi
Once DejaGNU is installed, you can run the tests in one of the
following ways:
- (1) cd gdb-6.6.90
+ (1) cd gdb-6.7
make check-gdb
or
- (2) cd gdb-6.6.90/gdb
+ (2) cd gdb-6.7/gdb
make check
or
- (3) cd gdb-6.6.90/gdb/testsuite
+ (3) cd gdb-6.7/gdb/testsuite
make site.exp (builds the site specific file)
runtest -tool gdb GDB=../gdb (or GDB=<somepath> as appropriate)
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.8684.2.17
diff -u -p -r1.8684.2.17 ChangeLog
--- ChangeLog 9 Oct 2007 18:03:29 -0000 1.8684.2.17
+++ ChangeLog 10 Oct 2007 17:02:54 -0000
@@ -1,3 +1,7 @@
+2007-10-10 Joel Brobecker <brobecker@adacore.com>
+
+ * README: Update GDB version number to 6.7.
+
2007-10-09 Daniel Jacobowitz <dan@codesourcery.com>
* solib-svr4.c (enable_break): Add the dynamic linker also if
^ permalink raw reply [flat|nested] 7+ messages in thread* [commit/branch] Update GDB version in README
@ 2006-11-20 0:30 Joel Brobecker
2006-11-20 1:36 ` Daniel Jacobowitz
0 siblings, 1 reply; 7+ messages in thread
From: Joel Brobecker @ 2006-11-20 0:30 UTC (permalink / raw)
To: gdb-patches
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
Just did an update of the version number in the README file. I still
need to take care of making this happen automatically, but that will
be for another day.
2006-11-19 Joel Brobecker <brobecker@adacore.com>
* README: Update GDB version number to 6.6.
--
Joel
[-- Attachment #2: README.diff --]
[-- Type: text/plain, Size: 10602 bytes --]
Index: README
===================================================================
RCS file: /cvs/src/src/gdb/README,v
retrieving revision 1.37
diff -u -p -r1.37 README
--- README 8 Aug 2006 20:26:23 -0000 1.37
+++ README 20 Nov 2006 00:24:42 -0000
@@ -1,4 +1,4 @@
- README for gdb-6.3 release
+ README for gdb-6.6 release
Updated 8, November, 2004 by Andrew Cagney
This is GDB, the GNU source-level debugger.
@@ -20,7 +20,7 @@ Unpacking and Installation -- quick over
In this release, the GDB debugger sources, the generic GNU include
files, the BFD ("binary file description") library, the readline
library, and other libraries all have directories of their own
-underneath the gdb-6.3 directory. The idea is that a variety of GNU
+underneath the gdb-6.6 directory. The idea is that a variety of GNU
tools can share a common copy of these things. Be aware of variation
over time--for example don't try to build gdb with a copy of bfd from
a release other than the gdb release (such as a binutils release),
@@ -29,8 +29,8 @@ Configuration scripts and makefiles exis
directory tree and automatically build all the pieces in the right
order.
- When you unpack the gdb-6.3.tar.gz file, you'll find a directory
-called `gdb-6.3', which contains:
+ When you unpack the gdb-6.6.tar.gz file, you'll find a directory
+called `gdb-6.6', which contains:
COPYING config-ml.in gettext.m4 ltconfig sim
COPYING.LIB config.guess include ltmain.sh src-release
@@ -43,7 +43,7 @@ called `gdb-6.3', which contains:
You can build GDB right in the source directory:
- cd gdb-6.3
+ cd gdb-6.6
./configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
@@ -57,25 +57,25 @@ You can build GDB in any empty build dir
mkdir build
cd build
- <full path to your sources>/gdb-6.3/configure
+ <full path to your sources>/gdb-6.6/configure
make
cp gdb/gdb /usr/local/bin/gdb (or wherever you want)
(Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
-different; see the file gdb-6.3/gdb/config/djgpp/README for details.)
+different; see the file gdb-6.6/gdb/config/djgpp/README for details.)
This will configure and build all the libraries as well as GDB. If
`configure' can't determine your system type, specify one as its
argument, e.g., `./configure sun4' or `./configure decstation'.
- Make sure that your 'configure' line ends in 'gdb-6.3/configure':
+ Make sure that your 'configure' line ends in 'gdb-6.6/configure':
- /berman/migchain/source/gdb-6.3/configure # RIGHT
- /berman/migchain/source/gdb-6.3/gdb/configure # WRONG
+ /berman/migchain/source/gdb-6.6/configure # RIGHT
+ /berman/migchain/source/gdb-6.6/gdb/configure # WRONG
The gdb package contains several subdirectories, such as 'gdb',
'bfd', and 'readline'. If your 'configure' line ends in
-'gdb-6.3/gdb/configure', then you are configuring only the gdb
+'gdb-6.6/gdb/configure', then you are configuring only the gdb
subdirectory, not the whole gdb package. This leads to build errors
such as:
@@ -111,7 +111,7 @@ documentation and TeX (or `texi2roff') t
GDB includes an already formatted copy of the on-line Info version
of this manual in the `gdb/doc' subdirectory. The main Info file is
-`gdb-6.3/gdb/doc/gdb.info', and it refers to subordinate files
+`gdb-6.6/gdb/doc/gdb.info', and it refers to subordinate files
matching `gdb.info*' in the same directory. If necessary, you can
print out these files, or read them with any editor; but they are
easier to read using the `info' subsystem in GNU Emacs or the
@@ -123,7 +123,7 @@ Info formatting programs, such as `texin
`makeinfo'.
If you have `makeinfo' installed, and are in the top level GDB
-source directory (`gdb-6.3', in the case of version 6.3), you can make
+source directory (`gdb-6.6', in the case of version 6.6), you can make
the Info file by typing:
cd gdb/doc
@@ -132,7 +132,7 @@ the Info file by typing:
If you want to typeset and print copies of this manual, you need
TeX, a program to print its DVI output files, and `texinfo.tex', the
Texinfo definitions file. This file is included in the GDB
-distribution, in the directory `gdb-6.3/texinfo'.
+distribution, in the directory `gdb-6.6/texinfo'.
TeX is a typesetting program; it does not print files directly, but
produces output files called DVI files. To print a typeset document,
@@ -146,11 +146,11 @@ without any extension or a `.dvi' extens
This file tells TeX how to typeset a document written in Texinfo
format. On its own, TeX cannot read, much less typeset a Texinfo file.
`texinfo.tex' is distributed with GDB and is located in the
-`gdb-6.3/texinfo' directory.
+`gdb-6.6/texinfo' directory.
If you have TeX and a DVI printer program installed, you can typeset
and print this manual. First switch to the the `gdb' subdirectory of
-the main source directory (for example, to `gdb-6.3/gdb') and then type:
+the main source directory (for example, to `gdb-6.6/gdb') and then type:
make doc/gdb.dvi
@@ -173,43 +173,43 @@ preparing GDB for installation; you can
a single directory, whose name is usually composed by appending the
version number to `gdb'.
- For example, the GDB version 6.3 distribution is in the `gdb-6.3'
+ For example, the GDB version 6.6 distribution is in the `gdb-6.6'
directory. That directory contains:
-`gdb-6.3/{COPYING,COPYING.LIB}'
+`gdb-6.6/{COPYING,COPYING.LIB}'
Standard GNU license files. Please read them.
-`gdb-6.3/bfd'
+`gdb-6.6/bfd'
source for the Binary File Descriptor library
-`gdb-6.3/config*'
+`gdb-6.6/config*'
script for configuring GDB, along with other support files
-`gdb-6.3/gdb'
+`gdb-6.6/gdb'
the source specific to GDB itself
-`gdb-6.3/include'
+`gdb-6.6/include'
GNU include files
-`gdb-6.3/libiberty'
+`gdb-6.6/libiberty'
source for the `-liberty' free software library
-`gdb-6.3/opcodes'
+`gdb-6.6/opcodes'
source for the library of opcode tables and disassemblers
-`gdb-6.3/readline'
+`gdb-6.6/readline'
source for the GNU command-line interface
NOTE: The readline library is compiled for use by GDB, but will
not be installed on your system when "make install" is issued.
-`gdb-6.3/sim'
+`gdb-6.6/sim'
source for some simulators (ARM, D10V, SPARC, M32R, MIPS, PPC, V850, etc)
-`gdb-6.3/texinfo'
+`gdb-6.6/texinfo'
The `texinfo.tex' file, which you need in order to make a printed
manual using TeX.
-`gdb-6.3/etc'
+`gdb-6.6/etc'
Coding standards, useful files for editing GDB, and other
miscellanea.
@@ -219,14 +219,14 @@ MS-DOS/MS-Windows are in the file gdb/co
The simplest way to configure and build GDB is to run `configure'
from the `gdb-VERSION-NUMBER' source directory, which in this example
-is the `gdb-6.3' directory.
+is the `gdb-6.6' directory.
First switch to the `gdb-VERSION-NUMBER' source directory if you are
not already in it; then run `configure'.
For example:
- cd gdb-6.3
+ cd gdb-6.6
./configure
make
@@ -242,8 +242,8 @@ you may need to run `sh' on it explicitl
sh configure
If you run `configure' from a directory that contains source
-directories for multiple libraries or programs, such as the `gdb-6.3'
-source directory for version 6.3, `configure' creates configuration
+directories for multiple libraries or programs, such as the `gdb-6.6'
+source directory for version 6.6, `configure' creates configuration
files for every directory level underneath (unless you tell it not to,
with the `--norecursion' option).
@@ -251,10 +251,10 @@ with the `--norecursion' option).
directories in the GDB distribution, if you only want to configure that
subdirectory; but be sure to specify a path to it.
- For example, with version 6.3, type the following to configure only
+ For example, with version 6.6, type the following to configure only
the `bfd' subdirectory:
- cd gdb-6.3/bfd
+ cd gdb-6.6/bfd
../configure
You can install `gdb' anywhere; it has no hardwired paths. However,
@@ -283,13 +283,13 @@ directory. If the path to `configure' w
argument to `--srcdir', you can leave out the `--srcdir' option; it
will be assumed.)
- For example, with version 6.3, you can build GDB in a separate
+ For example, with version 6.6, you can build GDB in a separate
directory for a Sun 4 like this:
- cd gdb-6.3
+ cd gdb-6.6
mkdir ../gdb-sun4
cd ../gdb-sun4
- ../gdb-6.3/configure
+ ../gdb-6.6/configure
make
When `configure' builds a configuration using a remote source
@@ -310,8 +310,8 @@ called `configure' (or one of its subdir
The `Makefile' that `configure' generates in each source directory
also runs recursively. If you type `make' in a source directory such
-as `gdb-6.3' (or in a separate configured directory configured with
-`--srcdir=PATH/gdb-6.3'), you will build all the required libraries,
+as `gdb-6.6' (or in a separate configured directory configured with
+`--srcdir=PATH/gdb-6.6'), you will build all the required libraries,
and then build GDB.
When you have multiple hosts or targets configured in separate
@@ -354,7 +354,7 @@ you can use it to test your guesses on a
Invalid configuration `i786v': machine `i786v' not recognized
`config.sub' is also distributed in the GDB source directory
-(`gdb-6.3', for version 6.3).
+(`gdb-6.6', for version 6.6).
`configure' options
@@ -482,7 +482,7 @@ As an alternative, the bug report can be
address "bug-gdb@gnu.org".
When submitting a bug, please include the GDB version number (e.g.,
-gdb-6.3), and how you configured it (e.g., "sun4" or "mach386 host,
+gdb-6.6), and how you configured it (e.g., "sun4" or "mach386 host,
i586-intel-synopsys target"). Since GDB now supports so many
different configurations, it is important that you be precise about
this. If at all possible, you should include the actual banner that
@@ -537,17 +537,17 @@ ftp://sources.redhat.com/pub/dejagnu/ wi
Once DejaGNU is installed, you can run the tests in one of the
following ways:
- (1) cd gdb-6.3
+ (1) cd gdb-6.6
make check-gdb
or
- (2) cd gdb-6.3/gdb
+ (2) cd gdb-6.6/gdb
make check
or
- (3) cd gdb-6.3/gdb/testsuite
+ (3) cd gdb-6.6/gdb/testsuite
make site.exp (builds the site specific file)
runtest -tool gdb GDB=../gdb (or GDB=<somepath> as appropriate)
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [commit/branch] Update GDB version in README
2006-11-20 0:30 Joel Brobecker
@ 2006-11-20 1:36 ` Daniel Jacobowitz
2006-11-20 5:57 ` Joel Brobecker
0 siblings, 1 reply; 7+ messages in thread
From: Daniel Jacobowitz @ 2006-11-20 1:36 UTC (permalink / raw)
To: Joel Brobecker; +Cc: gdb-patches
On Sun, Nov 19, 2006 at 04:30:20PM -0800, Joel Brobecker wrote:
> Just did an update of the version number in the README file. I still
> need to take care of making this happen automatically, but that will
> be for another day.
At the time, you might want to see how much of the text is still
relevant - I bet some of it isn't any more.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2008-03-13 17:42 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-09-19 19:49 [commit/branch] Update GDB version in README Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2008-03-13 17:42 Joel Brobecker
2007-10-29 17:55 Joel Brobecker
2007-10-10 17:20 Joel Brobecker
2006-11-20 0:30 Joel Brobecker
2006-11-20 1:36 ` Daniel Jacobowitz
2006-11-20 5:57 ` Joel Brobecker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox