From: Pedro Alves <palves@redhat.com>
To: Julian Smith <jules@op59.net>
Cc: gdb@sourceware.org
Subject: Re: Building current gdb on centos-5
Date: Thu, 30 May 2013 08:08:00 -0000 [thread overview]
Message-ID: <51A708FA.1070404@redhat.com> (raw)
In-Reply-To: <20130529215013.70904c7d.jules@op59.net>
On 05/29/2013 09:50 PM, Julian Smith wrote:
> Is the latest gdb in cvs, expected to build on centos-5 ?
It should, but looks like I broke it.
> I'm seeing this build failure:
>
> ...
> gcc -g -O2 -I. -I. -I./common -I./config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I./../include/opcode -I./../opcodes/.. -I./../readline/.. -I../bfd -I./../bfd -I./../include -I../libdecnumber -I./../libdecnumber -I./gn
> ulib/import -Ibuild-gnulib/import -DTUI=1 -I/usr/include/python2.4 -I/usr/include/python2.4 -Wall -Wdeclaration-after-statement -Wpointer-arith -Wpointer-sign -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts
> -Wmissing-prototypes -Wdeclaration-after-statement -Wformat-nonliteral -c -o mi-main.o -MT mi-main.o -MMD -MP -MF .deps/mi-main.Tpo ./mi/mi-main.c
> In file included from ./mi/mi-main.c:56:
> ./python/python-internal.h: In function 'gdb_Py_DECREF':
> ./python/python-internal.h:179: warning: dereferencing 'void *' pointer
> ./python/python-internal.h:179: error: request for member 'ob_refcnt' in something not a structure or union
Thanks. gdb_Py_DECREF is a recent addition:
/* Python 2.6 did not wrap Py_DECREF in 'do {...} while (0)', leading
to 'suggest explicit braces to avoid ambiguous ‘else’' gcc errors.
Wrap it ourselves, so that callers don't need to care. */
static inline void
gdb_Py_DECREF (void *op) /* ARI: editCase function */
{
Py_DECREF (op);
}
Making that:
- Py_DECREF (op);
+ Py_DECREF ((PyObject*) op);
should fix this. I'll push a fix.
On my system's Python 2.7, Py_DECREF always casts its argument
to (PyObject*), so it didn't seem necessary to cast it ourselves:
#define Py_DECREF(op) \
do { \
if (_Py_DEC_REFTOTAL _Py_REF_DEBUG_COMMA \
--((PyObject*)(op))->ob_refcnt != 0) \
_Py_CHECK_REFCNT(op) \
else \
_Py_Dealloc((PyObject *)(op)); \
} while (0)
> My centos-5 has python-2.4 (python-devel.i386 2.4.3-24.el5).
For the archives, could you please paste what Py_DECREF looks
like in 2.4? Thanks!
--
Pedro Alves
next prev parent reply other threads:[~2013-05-30 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 21:35 Julian Smith
2013-05-30 8:08 ` Pedro Alves [this message]
2013-05-30 8:14 ` Pedro Alves
2013-05-30 8:35 ` Julian Smith
2013-05-30 8:59 ` Pedro Alves
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=51A708FA.1070404@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=jules@op59.net \
/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