From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [commit] fix typo in _FILE_OFFSET_BITS comment
Date: Tue, 26 Oct 2010 18:09:00 -0000 [thread overview]
Message-ID: <1288116570-3634-1-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <4CA67482.7010206@vmware.com>
This fixes a typo that MichaelS noticed in a patch I submitted and
forgot to fix.
gdb/ChangeLog:
* (_FILE_OFFSET_BITS): Fix typo in comment.
Checked in.
---
gdb/ChangeLog | 4 ++++
gdb/python/python-internal.h | 2 +-
2 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4bfe017..8dcbd1a 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,9 @@
2010-10-26 Joel Brobecker <brobecker@adacore.com>
+ * (_FILE_OFFSET_BITS): Fix typo in comment.
+
+2010-10-26 Joel Brobecker <brobecker@adacore.com>
+
* python/python-internal.h (_FILE_OFFSET_BITS): Undefine.
(PyEval_InitThreads): Remove duplicate. Define as nothing.
(PyEval_ReleaseLock): Define as nothing.
diff --git a/gdb/python/python-internal.h b/gdb/python/python-internal.h
index e18f50a..67de622 100644
--- a/gdb/python/python-internal.h
+++ b/gdb/python/python-internal.h
@@ -38,7 +38,7 @@
/* On sparc-solaris, /usr/include/sys/feature_tests.h defines
_FILE_OFFSET_BITS, which pyconfig.h also defines. Same work
- arount technique as above. */
+ around technique as above. */
#undef _FILE_OFFSET_BITS
#if HAVE_LIBPYTHON2_4
--
1.7.1
next prev parent reply other threads:[~2010-10-26 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 23:36 [patch] Fix build failures with python support on sparc-solaris Joel Brobecker
2010-10-01 23:53 ` Michael Snyder
2010-10-26 18:09 ` Joel Brobecker [this message]
2010-10-26 18:08 ` Joel Brobecker
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=1288116570-3634-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.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