From: Simon Marchi <simon.marchi@polymtl.ca>
To: Nilufar Ferdous <nferdous@ucsc.edu>
Cc: gdb-patches@sourceware.org
Subject: Re: _PyImport_FixupBuiltin (gdb_module, "_gdb") error
Date: Fri, 21 Sep 2018 11:18:00 -0000 [thread overview]
Message-ID: <5e4f28ea59b390a3d89a9caab7874232@polymtl.ca> (raw)
In-Reply-To: <CABLnwaJ=78kYDqLgfc=ZtfkLG=4ZCRKAOz_3opGSBjPyM40K-Q@mail.gmail.com>
On 2018-09-21 01:23, Nilufar Ferdous wrote:
> Hi,
> I got this link
> https://sourceware.org/ml/gdb-patches/2018-05/msg00863.html
> Plese let me know how to solve this.
> I am getting error building rocket chip generator.
> gdb/gdb/python/python.c:1584:45: error: too few arguments to function
> 'int
> _PyImport_FixupBuiltin(PyObject*, const char*, PyObject*)'
> _PyImport_FixupBuiltin (gdb_module, "_gdb");
> ^
> In file included from /usr/include/python3.7m/Python.h:126,
> from
> /soe/nferdous/rocket-chip/riscv-tools/riscv-gnu-toolchain/build/../riscv-binutils-gdb/gdb/python/python-internal.h:94,
> from
> /soe/nferdous/rocket-chip/riscv-tools/riscv-gnu-toolchain/build/../riscv-binutils-gdb/gdb/python/python.c:94:
> /usr/include/python3.7m/import.h:115:17: note: declared here
> PyAPI_FUNC(int) _PyImport_FixupBuiltin(
> ^~~~~~~~~~~~~~~~~~~~~~
> make[3]: *** [Makefile:1947: python.o] Error 1
> make[2]: *** [Makefile:10420: all-gdb] Error 2
> make[1]: *** [Makefile:849: all] Error 2
> Thanks!
> Nilufar
This has been fixed in gdb 8.2. Here's the commit in case you want to
backport it.
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=aeab512851bf6ed623d1c6c4305b6ce05e51a10c
Simon
prev parent reply other threads:[~2018-09-21 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 5:23 Nilufar Ferdous
2018-09-21 11:18 ` Simon Marchi [this message]
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=5e4f28ea59b390a3d89a9caab7874232@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=nferdous@ucsc.edu \
/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