public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>, tim.wiederhake@intel.com
Cc: gdb-patches@sourceware.org, markus.t.metzger@intel.com
Subject: Re: MemoryView missing from Python 2.4 and 2.6
Date: Thu, 23 Feb 2017 22:59:00 -0000	[thread overview]
Message-ID: <20170223225946.snir4ab6twc7vo7n@localhost> (raw)
In-Reply-To: <87o9xsx38r.fsf@oracle.com>

On 17-02-23 17:48:20, Jose E. Marchesi wrote:
> While building git GDB on a certain distribution that features Python
> 2.6.6 (I know, ancient) we triggered a build failure:
> 
> g++  -g -O2   -I. -I../../gdb -I../../gdb/common -I../../gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I../../gdb/../include/opcode -I../../gdb/../opcodes/.. -I../../gdb/../readline/.. -I../../gdb/../zlib -I../bfd -I../../gdb/../bfd -I../../gdb/../include -I../libdecnumber -I../../gdb/../libdecnumber  -I../../gdb/gnulib/import -Ibuild-gnulib/import   -DTUI=1  -I/usr/include/python2.6 -I/usr/include/python2.6 -Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts -Wempty-body -Wunused-but-set-parameter -Wunused-but-set-variable -Wno-sign-compare -Wno-write-strings -Wno-narrowing -Wformat-nonliteral -Werror -c -o py-record-btrace.o -MT py-record-btrace.o -MMD -MP -MF .deps/py-record-btrace.Tpo -fno-strict-aliasing -DNDEBUG -fwrapv ../../gdb/python/py-record-btrace.c
> ../../gdb/python/py-record-btrace.c: In function ???PyObject* btpy_insn_data(PyObject*, void*)???:
> ../../gdb/python/py-record-btrace.c:333:10: error: ???PyMemoryView_FromObject??? was not declared in this scope
>    return PyMemoryView_FromObject (object);
>           ^~~~~~~~~~~~~~~~~~~~~~~
> ../../gdb/python/py-record-btrace.c:333:10: note: suggested alternative: ???PyBuffer_FromObject???
>    return PyMemoryView_FromObject (object);
>           ^~~~~~~~~~~~~~~~~~~~~~~
>           PyBuffer_FromObject
> make: *** [py-record-btrace.o] Error 1
> 
> Looks like the Memory View object was introduced in Python 2.7.

Hi Tim,
Could you take a look?

-- 
Yao 

  parent reply	other threads:[~2017-02-23 22:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 16:48 Jose E. Marchesi
2017-02-23 17:06 ` Jose E. Marchesi
2017-02-23 22:59 ` Yao Qi [this message]
2017-02-24 10:37   ` Wiederhake, Tim
2017-02-24 16:06     ` Yao Qi
2017-02-24 16:14       ` Paul.Koning
2017-02-28 10:53       ` Wiederhake, Tim
2017-02-28 12:51         ` Jose E. Marchesi
2017-03-07  0:21           ` Joel Brobecker
2017-03-07 13:38             ` Wiederhake, Tim
2017-03-07 15:27               ` Joel Brobecker
2017-03-03 10:21         ` Yao Qi
2017-03-06  8:56           ` Wiederhake, Tim
2017-03-07 10:32             ` Yao Qi
2017-03-07 17:18               ` Wiederhake, Tim
2017-03-17 15:59                 ` Yao Qi
2017-03-17 16:39                   ` Jose E. Marchesi
2017-03-20  9:04             ` Yao Qi
2017-03-20 22:44               ` Yao Qi

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=20170223225946.snir4ab6twc7vo7n@localhost \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=markus.t.metzger@intel.com \
    --cc=tim.wiederhake@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).