From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix build failures with python support on sparc-solaris
Date: Fri, 01 Oct 2010 23:53:00 -0000 [thread overview]
Message-ID: <4CA67482.7010206@vmware.com> (raw)
In-Reply-To: <1285976168-4119-1-git-send-email-brobecker@adacore.com>
Joel Brobecker wrote:
> Hello,
>
> This is something that I'd like to commit in a few days, bearing
> suggestions.
>
> There were two types of errors, mostly compiler warnings:
>
> 1. _FILE_OFFSET_BITS being redefined in pyconfig.h;
> This is a problem we're familiar with, having seen similar
> issues on GNU/Linux systems. I used a similar solution.
>
> 2. GCC 4.5 complains that calls to PyEval_InitThreads and
> PyEval_ReleaseLock have no effect. This is because our Python
> is built without thread support, leading us to use the dummy
> #define in python-internal.h which just gets replaced by `0'.
> Since this function returns void (checked versions 2.4 and 2.7),
> I simply removed the 0.
>
> gdb/ChangeLog:
>
> python/python-internal.h (_FILE_OFFSET_BITS): Undefine.
> (PyEval_InitThreads): Remove duplicate. Define as nothing.
> (PyEval_ReleaseLock): Define as nothing.
>
> Tested on x86_64-linux.
>
> ---
> gdb/python/python-internal.h | 10 +++++++---
> 1 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/gdb/python/python-internal.h b/gdb/python/python-internal.h
> index c5d1e73..97ac2fd 100644
> --- a/gdb/python/python-internal.h
> +++ b/gdb/python/python-internal.h
> @@ -36,6 +36,11 @@
> #undef _POSIX_C_SOURCE
> #undef _XOPEN_SOURCE
>
> +/* 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".
> +#undef _FILE_OFFSET_BITS
> +
> #if HAVE_LIBPYTHON2_4
> #include "python2.4/Python.h"
> #include "python2.4/frameobject.h"
> @@ -63,10 +68,9 @@ typedef int Py_ssize_t;
> #ifndef WITH_THREAD
> #define PyGILState_Ensure() ((PyGILState_STATE) 0)
> #define PyGILState_Release(ARG) ((void)(ARG))
> -#define PyEval_InitThreads() 0
> +#define PyEval_InitThreads()
> #define PyThreadState_Swap(ARG) ((void)(ARG))
> -#define PyEval_InitThreads() 0
> -#define PyEval_ReleaseLock() 0
> +#define PyEval_ReleaseLock()
> #endif
>
> /* In order to be able to parse symtab_and_line_to_sal_object function
next prev parent reply other threads:[~2010-10-01 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 23:36 Joel Brobecker
2010-10-01 23:53 ` Michael Snyder [this message]
2010-10-26 18:09 ` [commit] fix typo in _FILE_OFFSET_BITS comment Joel Brobecker
2010-10-26 18:08 ` [patch] Fix build failures with python support on sparc-solaris 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=4CA67482.7010206@vmware.com \
--to=msnyder@vmware.com \
--cc=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