This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author chaselton
Recipients chaselton, ethan.furman, freakboy3742, r.david.murray, refi64
Date 2015-06-30.15:09:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <64983CB3-7254-4988-90B6-9D6AD0C99547@gmail.com>
In-reply-to <89E3B300-7997-406C-8E06-C483CA794F51@gmail.com>
Content
On June 30, 2015 9:20:45 AM CDT, Ryan Gonzalez <report@bugs.python.org> wrote:
>
>Ryan Gonzalez added the comment:
>
>On June 30, 2015 8:14:34 AM CDT, Cyd Haselton <report@bugs.python.org>
>wrote:
>>
>>Cyd Haselton added the comment:
>>
>>Your question about -fPIE brings up a question: How should the
>>differences between Android 5 and previous versions be handled in
>>regards to this issue?
>>
>>Other than mandatory -fPIE, there are changes to Android[s libc that
>>may make  patches for python on Android 4.x incompatible with Android
>>5.
>>
>
>WHAT??? :( I can't find a list anywhere; how do you know?
>

I tried building GCC for Android 5 on device and ran into a bunch of errors like 'undefined symbol __swbuf.'  Googling the errors led to this page: https://developer.android.com/ndk/downloads/revision_history.html.

Relevant Part here:

" Removed the following symbols from all architectures: get_malloc_leak_info,free_malloc_leak_info, __srget, __swbuf, __srefill,__swsetup, __sdidinit, __sflags, __sfp, __sinit, __smakebuf,__sflush, __sread, __swrite, __sseek, __sclose, _fwalk,__sglue, __get_thread, __wait4, __futex_wake, __open,__get_tls, __getdents64, and dlmalloc."

>>Thoughts?
>
>Not really...

Would setting up two repos be advisable...one for 5 and one for 4.x and earlier?
>
>>
>>On June 29, 2015 9:29:35 AM CDT, Cyd Haselton <report@bugs.python.org>
>>wrote:
>>>
>>>Cyd Haselton added the comment:
>>>
>>>No...haven't upgraded to Android 5.0 yet.  
>>>
>>>On June 29, 2015 9:00:01 AM CDT, Ryan Gonzalez
>><report@bugs.python.org>
>>>wrote:
>>>>
>>>>Ryan Gonzalez added the comment:
>>>>
>>>>You compiled with -fPIE and GCC, right? I know the Android Clang
>>seems
>>>>broken.
>>>>
>>>>On June 29, 2015 7:09:25 AM CDT, Cyd Haselton
>><report@bugs.python.org>
>>>>wrote:
>>>>>
>>>>>Cyd Haselton added the comment:
>>>>>
>>>>>FYI, Figured out that running ./configure with --with-pydebug does
>>>NOT
>>>>>define Py_DEBUG in pyconfig.h.
>>>>>
>>>>>Defining it in pyconfig.h got me past the "undefined reference to
>>>>>`_PyUnicode_CheckConsistency'" error, but i'm now getting this:
>>>>>
>>>>>if test $? -ne 0 ; then \
>>>>>        echo "generate-posix-vars failed" ; \
>>>>>        rm -f ./pybuilddir.txt ; \
>>>>>        exit 1 ; \
>>>>>fi
>>>>>Debug memory block at address p=0x90b7b0: API ''
>>>>>    2416312320 bytes originally requested
>>>>>    The 3 pad bytes at p-3 are not all FORBIDDENBYTE (0xfb):
>>>>>        at p-3: 0x00 *** OUCH
>>>>>        at p-2: 0x00 *** OUCH
>>>>>        at p-1: 0x00 *** OUCH
>>>>> Because memory is corrupted at the start, the count of bytes
>>>>requested
>>>>>       may be bogus, and checking the trailing pad bytes may
>>>segfault.
>>>>>    The 4 pad bytes at tail=0x9096b7b0 are Segmentation fault
>>>>>generate-posix-vars failed
>>>>>make: *** [pybuilddir.txt] Error 1
>>>>>
>>>>>Will re-check patch application and try again
>>>>>
>>>>>----------
>>>>>
>>>>>_______________________________________
>>>>>Python tracker <report@bugs.python.org>
>>>>><http://bugs.python.org/issue23496>
>>>>>_______________________________________
>>>>
>>>>----------
>>>>
>>>>_______________________________________
>>>>Python tracker <report@bugs.python.org>
>>>><http://bugs.python.org/issue23496>
>>>>_______________________________________
>>>
>>>----------
>>>
>>>_______________________________________
>>>Python tracker <report@bugs.python.org>
>>><http://bugs.python.org/issue23496>
>>>_______________________________________
>>
>>----------
>>
>>_______________________________________
>>Python tracker <report@bugs.python.org>
>><http://bugs.python.org/issue23496>
>>_______________________________________
>
>----------
>
>_______________________________________
>Python tracker <report@bugs.python.org>
><http://bugs.python.org/issue23496>
>_______________________________________
History
Date User Action Args
2015-06-30 15:09:08chaseltonsetrecipients: + chaselton, r.david.murray, freakboy3742, ethan.furman, refi64
2015-06-30 15:09:08chaseltonlinkissue23496 messages
2015-06-30 15:09:07chaseltoncreate