Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
versions: +Python 3.6, Python 3.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavier de Gaye added the comment:
So the problem is that setup.py in build_extensions() does not build the
extensions that have been already built statically into the native Ubuntu
interpreter.
The solution is to build first natively from source python3.5 and set the PATH
environment
Xavier de Gaye added the comment:
I assume from your logs that a native (not the cross-built one) python3.5
already exists and is on your PATH.
What is the value of sys.builtin_module_names as given by this native python3.5
interpreter
Xavier de Gaye added the comment:
This new patch fixes the following:
* Use BASECFLAGS instead of CCSHARED.
* '-march=armv7-a' is not set in BASECFLAGS anymore as this is redundant: this
option is already set in the configure command line or is implicitly set by the
the first component
Xavier de Gaye added the comment:
See also the clang cross compilation documentation at
http://clang.llvm.org/docs/CrossCompilation.html.
--
versions: +Python 3.7 -Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Xavier de Gaye added the comment:
Your Setup file matches the one distributed with Python 3.5.2.
Did you get the Python source from https://www.python.org/ ?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
Please upload the output of make, this is where the error messages are printed
when extension modules fail to build.
Where is set the root directory for arm headers and libraries in the configure
command line ?
--
nosy: +xdegaye
Xavier de Gaye added the comment:
Fixed in issue 20766.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
stage: patch review -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
resolution: -> fixed
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Xavier de Gaye added the comment:
Thanks for the patch David, see my comment in Rietveld.
New patch based on David patch, just a bit simpler.
--
stage: patch review -> commit review
versions: +Python 3.7
Added file: http://bugs.python.org/file45067/test_getgroups_4.pa
Xavier de Gaye added the comment:
Uploaded refleak_5.patch with a simpler test case.
With the patch applied, './python -m test -R 3:3 test_pdb' runs with success.
The '_previous_sigint_handler' is reset at the Pdb prompt - instead of when the
signal is triggered - to handle the case where pdb
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
resolution: -> fixed
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Xavier de Gaye added the comment:
> And indeed, this changeset has removed entirely the doctests from the test
> suite :(
Entered new issue 28338.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Xavier de Gaye:
Changeset ee0bbfd972de in issue 18401 has removed the doctests from the pdb
test suite as can be seen by running test_pdb in verbose mode. See also
msg277864 that triggered the creation of this issue.
Nosying members of the issue 18401 nosy list
Xavier de Gaye added the comment:
Oh, test_pdb does not fail anymore in refleak mode as expected (see msg212510
for the change to apply to test_pdb.py in order to reproduce that). 'hg bisect'
says that this is happening since:
The first bad revision is:
changeset: 103552
Xavier de Gaye added the comment:
The problem may still be reproduced by running the attached pdb_refleak.py
script. Enter three times 'c' (short for the pdb 'continue' command) and the
following line is printed:
pdb 3 -> pdb 2 -> pdb 1
This shows that the third pdb instance
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +xdegaye
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28207>
___
__
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +xdegaye
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28190>
___
__
Xavier de Gaye added the comment:
> please try to build extension modules with mismatching abi flags (pydebug is
> the
relevant one). Post your results for both mismatch cases.
Hum, you are claiming that there is a problem with mismatching abi flags but
don't care to expla
Xavier de Gaye added the comment:
> but not having the existing cross build infrastructure being replaced by some
> new android concepts.
Running 'hg log' on configure.ac and Makefile.pre.in shows that there is not a
single change in the cross build infrastructure done for some new a
Xavier de Gaye added the comment:
What do you mean ? When cross-compiling, _PYTHON_HOST_PLATFORM is defined as
$MACHDEP-$_host_cpu, but _PYTHON_SYSCONFIGDATA_NAME is suffixed with
$(MACHDEP)_$(MULTIARCH) instead.
--
___
Python tracker <
Xavier de Gaye added the comment:
You do not answer my questions and resort to sarcasm instead: "How did you make
it more difficult?". I understand that you may be upset because issue 23968 has
been dismantled by the recent decision of removing the platdir files, but
please keep
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
dependencies: -byte-compile fails for cross-builds
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavier de Gaye added the comment:
Cross-compilation of Android x86_64 on a linux x86_64 host followed by 'make
install' does not fail anymore after the changes made in issue 27917. As
expected since the triplets are different now when the target is an Android
platform
Xavier de Gaye added the comment:
> Plus the abi flags should not be set by hand, you'll get in trouble at least
> for naming extensions, or building extensions for the wrong abi flags. This
> was an explicit decision when I first started adding the cross-build changes.
What do
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +xdegaye
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28125>
___
__
Xavier de Gaye added the comment:
Thanks for your help in testing these changes Chi Hsuan Yen.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27917>
___
_
Xavier de Gaye added the comment:
test_triplet_in_ext_suffix in test_sysconfig fails with the 'x86' Android
platform.
--
status: closed -> open
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Xavier de Gaye added the comment:
One of the test_sysconfig failed test is caused by the changes made in issue
27917. I will fix it there. The other one is caused by a change in my android
build setup that does not install anymore include/python3.6m/pyconfig.h, this
is fixed now and the test
Xavier de Gaye added the comment:
With the attached patch, the python test suite runs smoothly on android and
without errors on linux. On android, there are two new failed test cases in
test_sysconfig that I will look into later (in the frame of this issue, I guess
?), but otherwise about
Xavier de Gaye added the comment:
Confirming the problem reported by Chi Hsuan Yen. The attached patch fixes this.
Another problem is that the shared libraries names of the extension modules are
now suffixed with the wrong triplet, i.e. with the build system triplet instead
of the target host
Xavier de Gaye added the comment:
Sure, I was already planning to do it :)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
> Since the 3.6 cycle, these modules are regenerated for the build, so they are
> not outdated anymore. They are not a maintenance burden either.
Indeed, they are regenerated by the changes made in issue 23968 ("rename the
platform director
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +xdegaye
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28027>
___
__
Xavier de Gaye added the comment:
The problem is that Makefile and Modules/getpath.c are not consistent:
* Makefile uses $(LIBDIR)/python$(VERSION)/lib-dynload as the location of the
installed shared libraries and in this issue, it happens that LIBDIR is not
${exec_prefix}/lib
Xavier de Gaye added the comment:
The problem can be reproduced as follows:
Run the following commands to install python with a site configuration file
that installs the libraries to lib64:
export INSTALL_DIR=/some/path/to/install
mkdir -p $INSTALL_DIR/share
echo "test \&quo
Xavier de Gaye added the comment:
> Sorry that I haven't answered for a long time. I would like to get an email
> notification but I don't know whether/how I can enable it.
You should get an email upon each message posted to this issue. The email is
sent to the address you have regi
Xavier de Gaye added the comment:
> Just wondering, how you built Python with ncurses 6.0 Xavier?
I am using archlinux ncurses 6.0 [1] (sorry for the delay, no internet on a
sail crossing).
[1] https://www.archlinux.org/packages/core/x86_64/ncur
Xavier de Gaye added the comment:
issue #27659: Check for the existence of crypt()
--
dependencies: +Check for the existence of crypt()
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
> A question: should I include changes to configure and pyconfig.h.in in the
> patch?
You just need to mention that one should run autoreconf.
--
___
Python tracker <rep...@bugs.python.org>
<http://
Xavier de Gaye added the comment:
Patch rebased to current tip.
To summarize:
* The root cause of the problem reported by Benedikt still exists.
* The problem is hidden now that the shared libraries names include the
PLATFORM_TRIPLET.
* But byte-compilation still fails for cross-builds when
Xavier de Gaye added the comment:
It is also broken for gcc, see the buildbot 'compile' output.
It seems broken for all non windows builds whatever the compiler.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
The reason I would like this problem fixed is that the test suite is run on an
installed Python when cross-compiling, obviously you cannot run the test suite
with the cross-compiled Python on the source tree of the build system
Xavier de Gaye added the comment:
This problem occured for the first time on the "installed Python" buildbot
(setup by Zachary) at
http://buildbot.python.org/all/builders/x86%20Gentoo%20Installed%20with%20X%203.x/builds/747
on the day changeset 78d2cb7f66b6 has been commited (see
Xavier de Gaye added the comment:
We should wait for the pull request to be merged in the libffi development repo
before committing the patch. The PR is at
https://github.com/libffi/libffi/pull/265.
--
___
Python tracker <rep...@bugs.python.
Xavier de Gaye added the comment:
Thanks for the patch Chi Hsuan Yen!
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Xavier de Gaye added the comment:
> By msg264746, only ARM fails, so I patch libffi for arm and aarch64 triplets
> only
Why not for all Android architectures (*-linux-android*) as it is done in PR120
?
--
stage: -> patch review
___
Pytho
Xavier de Gaye added the comment:
Nice.
FWIW cross-compilation for Android works fine with comment-out-regen.patch.
> In native compiling mode, everything should be as normal. When
> cross-compiling, the rules for regenerating files should read like
>
> Python/importlib.h: # $
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +xdegaye
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27641>
___
__
Xavier de Gaye added the comment:
To reproduce the problem on any system where Python is built with configure:
$ mkdir -p tmp/build tmp/install
$ cd tmp
$ hg clone https://hg.python.org/cpython cpython
$ cd build
$ $(cd ../cpython && pwd)/configure --prefix=$(cd ../install &&a
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +haypo
stage: -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Xavier de Gaye added the comment:
Thanks for the review Martin. I will update the patch accordingly later.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +thomas-petazzoni
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27627>
___
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +thomas-petazzoni
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27606>
___
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +thomas-petazzoni
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22724>
___
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +thomas-petazzoni
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27453>
___
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +thomas-petazzoni
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue23968>
___
Xavier de Gaye added the comment:
> Some dependent issues, like issue26852, issue26859 and issue27640, are for
> reducing the size of an installation. How about moving them to another
> meta-issue? First they are not critical for normal usages on Android. Second
> they are
Xavier de Gaye added the comment:
Roman, can you please enter a new issue for that problem.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
> About doko's note and your response: unless this patch does not install the
> source (I haven't looked), the __pycache__ files *will* be rebuilt at
> interpreter start, according to the text you quoted.
Right, and since the source files ar
Xavier de Gaye added the comment:
> and if the only reason is to reduce space by omitting the source, then it
> should also not install the source so the name is wrong :)
I miss your point, msg271515 said earlier "the patch removes all *.py files".
The patch does a sourcel
Xavier de Gaye added the comment:
Yes, the packager must use appropriately either CFLAGS CPPFLAGS [1] and
LDFLAGS, or CC. I am using:
CC="clang --sysroot=$(SYSROOT) -target $(TARGET) -gcc-toolchain
$(GCC_TOOLCHAIN)".
[1] See issue 27453, for the remaining problem upon usin
Xavier de Gaye added the comment:
> but these are rebuilt when you start the interpreter, aren't they?
No.
Quoting PEP 3147:
Case 4: legacy pyc files and source-less imports
Python will ignore all legacy pyc files when a source file exists next to
it. In other words, if a foo.
Xavier de Gaye added the comment:
> I am still curious what configures the preprocessor to set __ARM_ARCH to 7 (I
> guess the clang -target argument?)
Yes, the -target clang argument or the -march gcc argument.
> and why we can’t set LDFLAGS at the same time or place. Is it
Xavier de Gaye added the comment:
> hmm, I really don't buy the space-saving argument. you are saving some space
> with shorter path names, nothing more. so why do you introduce this option?
No, compileall is run with '-b', so there are no PEP 3147 __pycache__
direc
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +haypo, thomas-petazzoni
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +haypo, thomas-petazzoni
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavier de Gaye added the comment:
issue #27640: add the '--disable-test-suite' option to configure
--
dependencies: +add the '--disable-test-suite' option to configure
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
Install byte-code files to their legacy locations and names to save space
(default are the PEP 3147 locations and names) when configure is run with
'--enable-legacy-pyc-files'.
The patch does not prevent ensurepip to use PEP 3147 locations and names when
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
components: +Cross-Build
nosy: +Alex.Willmer
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavier de Gaye <xdeg...@gmail.com>:
Added file: http://bugs.python.org/file43918/listdirs.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Xavier de Gaye:
Do not install the Python test suite when configure is run with
'--disable-test-suite'. This about divides by two the size of the installed
standard library.
Related to issue 26852: add the '--enable-legacy-pyc-files' option to configure.
The attached
Xavier de Gaye added the comment:
> After several years there is still no consenus, so make it simple - the popen
> and subprocess shell is one of /bin/sh, cmd.exe, or some other "hard-coded"
> shell.
I agree, the last patch that is being reviewed in issue 1
Xavier de Gaye added the comment:
Nice, the patch fixes the problem when python is built with gcc :)
Running test_ctypes on the Android emulator when python is built for the arm
architecture or the armv7 architecture gives in both cases the same successfull
result:
Ran 456 tests
Xavier de Gaye added the comment:
> Cross-compile CPython for ARM with clang fails in _ctypes due to
> https://llvm.org/bugs/show_bug.cgi?id=20595. This bug is already fixed in
> libffi.
I have entered issue 27627 for this problem.
--
nosy:
Xavier de Gaye added the comment:
See also msg 269907 and msg269908.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27627>
___
__
New submission from Xavier de Gaye:
The build is done with:
clang --sysroot=/opt/android-ndk/platforms/android-21/arch-arm -target
armv7-none-linux-androideabi -gcc-toolchain
/opt/android-ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64
The error message:
clang --sysroot=/opt
Xavier de Gaye added the comment:
issue #27627: clang fails to build ctypes on Android armv7
--
dependencies: +clang fails to build ctypes on Android armv7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
Thanks for looking into that problem.
Can you provide a patch ?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Xavier de Gaye added the comment:
New patch. The sed commands used to evaluate ANDROID_API_LEVEL and _arm_arch do
not need to discard comment lines and empty lines in the output of the
preprocessor.
--
Added file: http://bugs.python.org/file43893/build-flags_4.patch
Xavier de Gaye added the comment:
Thanks for the suggestion, I won't include them anymore in patches then.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
The test is already skipped by the patch, for Android API level < 23, with the
statement:
raise unittest.SkipTest("need working 'id -G'")
Do you mean that the test should be skipped instead more explicitly with
something li
Xavier de Gaye added the comment:
The first 'build-flags_3.patch' file that was uploaded did not get a review
button because ssh://h...@hg.python.org/cpython was down at that time.
The second upload has been successfull !
--
___
Python tracker <
Changes by Xavier de Gaye <xdeg...@gmail.com>:
Added file: http://bugs.python.org/file43878/build-flags_3.patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Xavier de Gaye added the comment:
> Hum, does the id program supports -G on Android?
It does on Android 6.0 but prints the same result as 'id' (without -G) on
previous Android versions.
Here is the output of the commands involved in the test for the root user on my
archlinux box, the Andr
Xavier de Gaye added the comment:
Thanks for the review and the suggestions Martin :)
New patch.
--
Added file: http://bugs.python.org/file43875/build-flags_3.patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
nosy: +haypo
stage: patch review -> commit review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Xavier de Gaye added the comment:
The reference to '-mthumb' in the ndk documentation:
https://developer.android.com/ndk/guides/standalone_toolchain.html#abi.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
issue #27606: Android cross-built for armv5te with clang and '-mthumb' crashes
with SIGSEGV or SIGILL
--
dependencies: +Android cross-built for armv5te with clang and '-mthumb' crashes
with SIGSEGV or SIGILL
Changes by Xavier de Gaye <xdeg...@gmail.com>:
Added file: http://bugs.python.org/file43859/logcat.txt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavier de Gaye <xdeg...@gmail.com>:
Added file: http://bugs.python.org/file43861/logcat-pydebug.txt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Xavier de Gaye:
Android ndk version r11c.
The crash happens very early on python startup. The SIGILL occurs when python
is built 'with-pydebug'.
Python runs fine on the armv5te emulator when built with clang without
'-mthumb'.
Python runs fine on the armv5te emulator
Changes by Xavier de Gaye <xdeg...@gmail.com>:
Added file: http://bugs.python.org/file43860/strace-pydebug.txt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by Xavier de Gaye <xdeg...@gmail.com>:
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Xavier de Gaye added the comment:
Patch with a new error message.
--
Added file: http://bugs.python.org/file43829/py_for_gen_26662_3.patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Xavier de Gaye added the comment:
> Is there a plan to make Android a supported platform in 3.6?
Answer in the Android meta-issue at msg 270942.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.or
Xavier de Gaye added the comment:
Larry asked in msg 270937:
> Is there a plan to make Android a supported platform in 3.6?
This is the list of Android related issues that will modify the standard
library and core Python when fixed:
issue 16255: subrocess.Popen needs /bin/sh but Andr
801 - 900 of 1485 matches
Mail list logo
