Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: gdb-patches@sourceware.cygnus.com
Subject: [PATCH+branch]: Minor tweaks for DJGPP README file
Date: Sun, 21 Oct 2001 07:23:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1011021162143.23661C-100000@is> (raw)

FYI: the below was committed today to both branch and head.

Index: src/gdb/config/djgpp/README
===================================================================
RCS file: /cvs/src/src/gdb/config/djgpp/README,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- README	2000/05/17 11:49:52	1.3
+++ README	2001/10/21 14:21:03	1.4
@@ -38,7 +38,7 @@
 (GCC, header files, and the libraries), and also DJGPP ports of the
 following tools:
 
-	- GNU Make 3.78.1 or later
+	- GNU Make 3.79.1 or later
 	- Bash 2.03 or later
 	- GNU Sed
 	- GNU Fileutils
@@ -62,7 +62,7 @@
 If you download the source distribution from one of the DJGPP sites,
 just unzip it while preserving the directory structure (I suggest to
 use unzip32.exe available with the rest of DJGPP), and proceed to the
-section "How to build" below.
+section "How to build", below.
 
 Source distributions downloaded from one of the GNU FTP sites need
 some more work to unpack.  First, you MUST use the `djunpack' batch
@@ -75,25 +75,26 @@
 necessary mappings.  So you need first to retrieve that batch file,
 and then invoke it to unpack the distribution.  Here's how:
 
- djtar -x -p -o gdb-5.0/djunpack.bat gdb-5.0.tar.gz > djunpack.bat
- djunpack gdb-5.0.tar.gz
+ djtar -x -p -o gdb-5.1/djunpack.bat gdb-5.1.tar.gz > djunpack.bat
+ djunpack gdb-5.1.tar.gz
 
 (The name of the distribution archive and the leading directory of the
 path to `djunpack.bat' in the distribution will be different for
-versions of GDB other than 5.0.)
+versions of GDB other than 5.1.)
 
 If the argument to `djunpack.bat' include leading directories, it MUST
 be given with the DOS-style backslashes; Unix-style forward slashes
 will NOT work.
 
-If the distribution comes as a .tar.bz2 archive, you need to unpack it
-as follows:
+If the distribution comes as a .tar.bz2 archive, and your version of
+`djtar' doesn't support bzip2 decompression, you need to unpack it as
+follows:
+
+ bnzip2 gdb-5.1.tar.bz2
+ djtar -x -p -o gdb-5.1/djunpack.bat gdb-5.1.tar > djunpack.bat
+ djunpack gdb-5.1.tar
 
- bnzip2 gdb-5.0.tar.bz2
- djtar -x -p -o gdb-5.0/djunpack.bat gdb-5.0.tar > djunpack.bat
- djunpack gdb-5.0.tar
 
-
 3. How to build
    ------------
 
@@ -105,7 +106,7 @@
 
 To build a package downloaded from a GNU FTP site, you will need o
 configure it first.  You will also need to configure it if you want to
-change the configuration options (e.g., compile with support for the
+change the configuration options (e.g., compile without support for the
 GDBMI interface).  To configure GDB, type this command:
 
 		sh ./gdb/config/djgpp/djconfig.sh
@@ -117,8 +118,8 @@
 
 You may pass optional switches to djconfig.sh.  It accepts all the
 switches accepted by the original GDB configure script.  These
-switches are described in the file gdb/README, and their full list be
-displayed by running the following command:
+switches are described in the file gdb/README, and their full list can
+be displayed by running the following command:
 
 		sh ./gdb/configure --help
 
@@ -126,13 +127,13 @@
 to the script the name of the directory where GDB sources are
 unpacked--even if you are building GDB in-place!  For example:
 
-	sh ./gdb/config/djgpp/djconfig.sh . --enable-gdbmi
+	sh ./gdb/config/djgpp/djconfig.sh . --disable-gdbmi
 
 It is also possible to build GDB in a directory that is different from
 the one where the sources were unpacked.  In that case, you have to
 pass the source directory as the first argument to the script:
 
-	sh ./gdb/config/djgpp/djconfig.sh d:/gnu/gdb-5.0
+	sh ./gdb/config/djgpp/djconfig.sh d:/gnu/gdb-5.1
 
 You MUST use forward slashes in the first argument.
 


                 reply	other threads:[~2001-10-21  7:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.SUN.3.91.1011021162143.23661C-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sourceware.cygnus.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