Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Brooks Moses <brooks@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [patch] Document that GDB does not assume GNU make.
Date: Wed, 07 Nov 2007 03:46:00 -0000	[thread overview]
Message-ID: <47313519.7000508@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

As Daniel Jacobowitz pointed out to me with regards to my recent
makefile patch, GDB (unlike GCC) does not assume that it is being built
with GNU make.  The current documentation does not comment on this point
one way or the other, and so I propose the attached patch to make this
clear.

Tested with "make pdf".  Ok to commit?

- Brooks

---------------------------------------------------------------------
2007-11-06  Brooks Moses  <brooks@codesourcery.com>

	* doc/gdb.texinfo (Requirements): Document that GDB
	should build with any POSIX-compliant make.

---------------------------------------------------------------------

[-- Attachment #2: 2007-11-06_doc_make.diff --]
[-- Type: text/plain, Size: 620 bytes --]

Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.441
diff -U3 -r1.441 gdb.texinfo
--- gdb/doc/gdb.texinfo	30 Oct 2007 19:35:35 -0000	1.441
+++ gdb/doc/gdb.texinfo	7 Nov 2007 03:09:19 -0000
@@ -22185,6 +22185,10 @@
 @value{GDBN} is written in ISO C90.  It should be buildable with any
 working C90 compiler, e.g.@: GCC.
 
+@item make
+The @value{GDBN} makefiles are compatible with any @sc{posix}-compliant
+implementation of make.
+
 @end table
 
 @heading Tools/Packages Optional for Building @value{GDBN}

             reply	other threads:[~2007-11-07  3:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07  3:46 Brooks Moses [this message]
2007-11-07  4:20 ` Eli Zaretskii

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=47313519.7000508@codesourcery.com \
    --to=brooks@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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