From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: archer@sourceware.org
Subject: [archer/tromey/python] python3 wchar_t
Date: Mon, 02 Feb 2015 22:46:00 -0000 [thread overview]
Message-ID: <20150202224636.GA27511@host1.jankratochvil.net> (raw)
Hi Phil,
for F-22/Rawhide we need to switch to Python3:
https://bugzilla.redhat.com/show_bug.cgi?id=1014549
But on F-21 or F-22:
# yum install python3-devel
$ cd archer-tromey-python
$ CFLAGS= ./configure --with-python=/usr/bin/python3
$ make
./python/python.c: In function ‘run_python_script’:
./python/python.c:1261:28: error: passing argument 2 of ‘PySys_SetArgv’ from incompatible pointer type [-Werror]
PySys_SetArgv (argc - 1, argv + 1);
/* Set up the Python argument vector and evaluate a script. This is
used to implement 'gdb -P'. */
run_python_script (int argc, char **argv)
PySys_SetArgv (argc - 1, argv + 1);
Primarily asking if the Fedora compatibility with 'gdb -P' is still required.
If yes then a patch is welcome or I can also fix that (mbstowcs()).
F-22 GDB will be only in DTS-4.0 (not DTS-3.x) so a backward compatibility for
DTS AFAIK should not be a concern.
Thanks,
Jan
next reply other threads:[~2015-02-02 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 22:46 Jan Kratochvil [this message]
2015-02-04 16:29 ` Jan Kratochvil
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=20150202224636.GA27511@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@sourceware.org \
--cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).