From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Regression for build --without-python [Re: RFC: fix atexit.register]
Date: Fri, 21 Sep 2012 07:05:00 -0000 [thread overview]
Message-ID: <20120921070501.GA4231@host2.jankratochvil.net> (raw)
In-Reply-To: <87y5k4tocb.fsf@fleche.redhat.com>
On Thu, 20 Sep 2012 22:45:56 +0200, Tom Tromey wrote:
> >>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:
>
> Tom> * NEWS: Update.
> Tom> * python/python.c (finalize_python): New function.
> Tom> (_initialize_python): Make a final cleanup.
>
> Tom> * gdb.python/python.exp: Test atexit.register.
>
> I'm checking this in.
./python/python.c: In function ‘finalize_python’:
./python/python.c:1280:3: warning: implicit declaration of function ‘PyGILState_Ensure’ [-Wimplicit-function-declaration]
./python/python.c:1281:3: error: ‘python_gdbarch’ undeclared (first use in this function)
./python/python.c:1281:3: note: each undeclared identifier is reported only once for each function it appears in
./python/python.c:1282:3: error: ‘python_language’ undeclared (first use in this function)
./python/python.c:1284:3: warning: implicit declaration of function ‘Py_Finalize’ [-Wimplicit-function-declaration]
./python/python.c: At top level:
./python/python.c:1273:1: warning: ‘finalize_python’ defined but not used [-Wunused-function]
Regards,
Jan
next prev parent reply other threads:[~2012-09-21 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 15:43 RFC: fix atexit.register Tom Tromey
2012-09-06 16:13 ` Eli Zaretskii
2012-09-10 19:40 ` Tom Tromey
2012-09-10 19:52 ` Eli Zaretskii
2012-09-20 20:46 ` Tom Tromey
2012-09-21 7:05 ` Jan Kratochvil [this message]
2012-11-29 19:13 ` [commit] Fix !HAVE_THREAD Python build error (Re: RFC: fix atexit.register) Ulrich Weigand
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=20120921070501.GA4231@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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