hose libraries...if
it does at all?
On Tue, Feb 3, 2015 at 12:10 AM, Eric Snow wrote:
> On Mon, Feb 2, 2015 at 12:36 PM, Cyd Haselton wrote:
>> After fixing a segfault issue (many thanks Ryan) I'm back to the same issue
>> I was having with Python 2.7.8; the newly built pyth
am.
>
>What exactly appears? Does it say anything about the source of the
>error?
>
>On Mon, Feb 2, 2015 at 3:24 PM, Cyd Haselton
>wrote:
>
>> No traceback unfortunately...the fakechroot in the environment throws
>the
>> error and setup.py fails.
>&
tKat running on an x86) here:
>https://github.com/wandering-logic/android_x86_python-3.4.
>
See answer above. I'm working in an environment on the Android device.
Hopefully this clarifies things. I'll re-post this over at python-sig.
>Best,
>-Matt
>
>From: Cyd Ha
email I send to python-sig
On February 3, 2015 12:10:54 AM CST, Eric Snow
wrote:
>On Mon, Feb 2, 2015 at 12:36 PM, Cyd Haselton
>wrote:
>> After fixing a segfault issue (many thanks Ryan) I'm back to the same
>issue
>> I was having with Python 2.7.8; the newly built py
ot
>really.
>
>What's the full traceback for the undefined reference exception?
>
>On Mon, Feb 2, 2015 at 2:04 PM, Cyd Haselton
>wrote:
>
>> Update: While waiting for replies I made the change referenced here:
>>
>https://bugs.python.org/review/5309/diff2/
et a terminating 'undefined reference to dlopen' error, but I do
get 'importing extensions failed' errors for each extension...like this:
*** WARNING: importing extension "_pickle" failed with : 'module' object has no attribute 'load'
On Februa
After fixing a segfault issue (many thanks Ryan) I'm back to the same issue I
was having with Python 2.7.8; the newly built python throws an undefined
reference to dlopen when running setup.py...specifically when importing
just-built extensions
I've managed to narrow the problem down to the fol
to figure out a way to get the instuctions you sent
>>implemented, but this may be a deal-breaker for porting Python 3.4.x
>>for me...I may go back to working on 2.7.x
>>
>>Sent from my android device.
>>
>>-Original Message-
>>From: Ryan Gonzalez
January 31, 2015 1:10:18 PM CST, Ryan wrote:
>No; I was looking for all uses of _PyRaw_Strdup. Surprisingly, it's
>used only a few times.
>
>Cyd Haselton wrote:
>>Question:
>>When you said earlier that you found the problem by using grep...were
>>you looking f
31, 2015 1:10:18 PM CST, Ryan wrote:
>No; I was looking for all uses of _PyRaw_Strdup. Surprisingly, it's
>used only a few times.
>
>Cyd Haselton wrote:
>>Question:
>>When you said earlier that you found the problem by using grep...were
>>you looking for place
d instructions that don't use the NDK.
>>
>> On Fri, Jan 30, 2015 at 6:19 PM, Cyd Haselton
>wrote:
>>
>>> This is going to take some time...here's why:
>>>
>>> Downloading and installing the NDK/SDK won't be too hard...I have to
>>&
linux-androideabi-gdb
>
> Now, GDB should have opened, so type the following commands:
>
> set solib-search-path
> file
> target remote :5055
> run
>
> Now, wait for the program to crash and type:
>
> backtrace
>
> You should now see a complete backtra
t;
>>> ...but I think I found the issue with grep. Try applying the attached patch
>>> to the Python/frozenmain.c. It comments out the locale handling.
>>>
>>> It seems that Python always calls its strdup function on the locale string.
>>> On Android, this c
> checks the length of the (possibly null) string argument first.
>
> Please try the patch I attached in the last email. It *might* fix the issue.
> Android has crappy locale handling.
>
> On Fri, Jan 30, 2015 at 12:09 PM, Cyd Haselton wrote:
>>
>> Un
Unfortunately it is still reporting the same function :-/.
On Fri, Jan 30, 2015 at 1:44 PM, Ryan Gonzalez wrote:
> Yes...
>
> Can you check if it's crashing in a different function now?
>
> On Fri, Jan 30, 2015 at 1:39 PM, Cyd Haselton wrote:
>>
>> Yes I d
Android has crappy locale handling.
>
> On Fri, Jan 30, 2015 at 12:09 PM, Cyd Haselton wrote:
>>
>> Unless i'm reading something incorrectly, _PyMem_RawStrdup is
>> currently returning NULL when given a null pointer.
>>
>> From obmalloc.c
>>
>
plicate a null pointer. Basically, it's probably the caller's fault.
>
> You could always try modifying _PyMem_RawStrdup to return NULL when given a
> null pointer and see where it then segfaults.
>
> On Fri, Jan 30, 2015 at 11:53 AM, Cyd Haselton wrote:
>>
>> Alterna
crash using gdb? Try the
> steps here.
>
> That way we can see where Python's own strdup function is getting called.
>
> On Fri, Jan 30, 2015 at 9:05 AM, Cyd Haselton wrote:
>>
>> Absolutely. Good thing I have addr2line on device
>>
>> /bld/python/Py
Alternatively, is there a hassle-free way to find out what changed in
obmalloc.c between 2.7.x and 3.4.x?
On Fri, Jan 30, 2015 at 9:29 AM, Cyd Haselton wrote:
> There's a related strdup patch for readline.c, mentioned
> here:http://bugs.python.org/issue21390 and here
> https://g
n...they're all prefixed
with _PyXx
On Fri, Jan 30, 2015 at 9:05 AM, Cyd Haselton wrote:
> Absolutely. Good thing I have addr2line on device
>
> /bld/python/Python-3.4.2 $ addr2line -C -f -e /lib/libpython3.4m.so.1.0
> 0008bbc8
> _PyMem_RawStrdup
> /bld/python/Python-3.4.2/Objec
the steps at http://stackoverflow.com/a/11369475/2097780? They
> allow you to get a better idea of where libc is crashing.
>
> Cyd Haselton wrote:
>>
>> Managed to get this out of logcat:
>> F(11914) Fatal signal 11 (SIGSEGV) at 0x (code=1), thread
>> 11914
as nothing to do with Python itself.
>
> Maybe this would be useful?
>
>>
>> That stack trace would be really helpful.
>>
>> On Wed, Jan 28, 2015 at 8:34 AM, Cyd Haselton wrote:
>>>
>>> Apologies...I'm not sure what a stack track is, but I
do with
> interprocess communication. Likely has nothing to do with Python itself.
>
> Maybe this would be useful?
>
>>
>> That stack trace would be really helpful.
>>
>> On Wed, Jan 28, 2015 at 8:34 AM, Cyd Haselton wrote:
>>>
>>> Apologies
ins it a bit (slides 24-29). Looks like something to do with
> interprocess communication. Likely has nothing to do with Python itself.
>
> Maybe this would be useful?
>
>>
>> That stack trace would be really helpful.
>>
>> On Wed, Jan 28, 2015 at 8:34 AM, Cyd Haselton
ows a syscall trace --
> also useful, but doesn't tell you precisely how it segfaulted.)
>
> On Wed, Jan 28, 2015 at 6:43 AM, Cyd Haselton wrote:
>>
>> All,
>> I recently ditched my attempts to port Python 2.7.8 to Android in
>> favor of Python 3.4.2. Unfortunate
All,
I recently ditched my attempts to port Python 2.7.8 to Android in
favor of Python 3.4.2. Unfortunately, after using the same configure
options in the same environment, and modifying the setup.py as needed,
the newly built binary throws a segfault when the generate-posix-vars
portion of the bu
On Tue, Jan 27, 2015 at 2:45 PM, Glenn Linderman wrote:
> On 1/27/2015 8:04 AM, Cyd Haselton wrote:
>
> Noted. Will proceed with the 3.x releass.
>
> I had been excited you were working on Android Python until I realized you
> were working on 2.x. I started with Python 3, and ha
On Tue, Jan 27, 2015 at 9:07 AM, Skip Montanaro
wrote:
> On Tue, Jan 27, 2015 at 6:46 AM, Cyd Haselton wrote:
>> A quick FYI: The decision to build 2.7.8 (instead of 3.x) on Android
>> was made after reading this article:
>> https://wiki.python.org/moin/Python2orPython3
>
On Tue, Jan 27, 2015 at 6:52 AM, Skip Montanaro
wrote:
> On Tue, Jan 27, 2015 at 6:31 AM, Cyd Haselton wrote:
>> Additionally it appears as though some modules were not built with the
>> correct links to -lc -ldl, even though I added them as dependencies in
>> Setup and se
On Tue, Jan 27, 2015 at 6:31 AM, Cyd Haselton wrote:
> On Mon, Jan 26, 2015 at 2:26 PM, Skip Montanaro
> wrote:
>> On Mon, Jan 26, 2015 at 12:49 PM, Cyd Haselton wrote:
>>> Unfortunately, as I quickly found out,
>>> Python's built-in help function requires
On Mon, Jan 26, 2015 at 2:26 PM, Skip Montanaro
wrote:
> On Mon, Jan 26, 2015 at 12:49 PM, Cyd Haselton wrote:
>> Unfortunately, as I quickly found out,
>> Python's built-in help function requires tkinter, which requires
>> tcl/tk.
>
> I'm a little confus
On Mon, Jan 26, 2015 at 2:25 PM, Zachary Ware
wrote:
> On Mon, Jan 26, 2015 at 12:49 PM, Cyd Haselton wrote:
>> Hello,
>> I've finally managed to build a (somewhat) working Python port for the
>> Android tablet I'm using. Unfortunately, as I quickly found out,
>
Hello,
I've finally managed to build a (somewhat) working Python port for the
Android tablet I'm using. Unfortunately, as I quickly found out,
Python's built-in help function requires tkinter, which requires
tcl/tk.
I did download the sources for tcl/tk and built tcl, but found out
that tk requir
gory P. Smith > > wrote:
>>
>> On Fri Jan 23 2015 at 11:20:02 AM M.-A. Lemburg > > wrote:
>>
>> On 23.01.2015 19:48, Matthias Klose wrote:
>> > On 01/23/2015 06:30 PM, Cyd Haselton wrote:
>> >> R
Since (judging from the lack of responses) setup.py can't be removed
from the Makefile, I kept troubleshooting.I've managed to get the
build to complete and make install runs instead of throwing an
undefined reference right off the bat, unfortunately I've run into the
following:
ImportError: No mo
roid (perhaps for security reasons)
> that's not true, if Z depends on A, then you need to have "-lA" when you link
> Z. An example (and patch) for this problem is
> http://bugs.python.org/issue21668.
>
> -Matt
>
>> -Original Message-
>
Replies in body of message for clarity:
On Sat, Jan 24, 2015 at 5:08 PM, Frank, Matthew I
wrote:
> Android's dlopen() works slightly differently than the normal Unix dlopen()
> in at least two different ways. I haven't seen your particular problem, but
> that's probably because I'm cross-build
> On 23.01.2015 19:48, Matthias Klose wrote:
>>>> > On 01/23/2015 06:30 PM, Cyd Haselton wrote:
>>>> >> Related to my earlier question regarding building Python on Android
>>>> >> and an undefined reference to dlopen error...I have the followi
On Fri, Jan 23, 2015 at 12:48 PM, Matthias Klose wrote:
> On 01/23/2015 06:30 PM, Cyd Haselton wrote:
>> Related to my earlier question regarding building Python on Android
>> and an undefined reference to dlopen error...I have the following
>> question: Is it possible
On Fri, Jan 23, 2015 at 12:48 PM, Matthias Klose wrote:
> On 01/23/2015 06:30 PM, Cyd Haselton wrote:
>> Related to my earlier question regarding building Python on Android
>> and an undefined reference to dlopen error...I have the following
>> question: Is it possible
On Fri, Jan 23, 2015 at 1:19 PM, M.-A. Lemburg wrote:
> On 23.01.2015 19:48, Matthias Klose wrote:
>> On 01/23/2015 06:30 PM, Cyd Haselton wrote:
>>> Related to my earlier question regarding building Python on Android
>>> and an undefined reference to dlopen e
On Fri, Jan 23, 2015 at 12:48 PM, Matthias Klose wrote:
> On 01/23/2015 06:30 PM, Cyd Haselton wrote:
>> Related to my earlier question regarding building Python on Android
>> and an undefined reference to dlopen error...I have the following
>> question: Is it possible
Related to my earlier question regarding building Python on Android
and an undefined reference to dlopen error...I have the following
question: Is it possible to build and install Python without having
to build and install...or use...distutils?
Some background:
I can build the python interpreter
world, not to Python.
>> (dlopen is used by a lot of systems, not just Python.)
>>
>> On Wed, Jan 21, 2015 at 2:43 PM, Cyd Haselton wrote:
>>>
>>> On Mon, Jan 19, 2015 at 5:23 PM, Cyd Haselton
>>> wrote:
>>> > On Mon, Jan 19, 2015 at 8:5
On Mon, Jan 19, 2015 at 5:23 PM, Cyd Haselton wrote:
> On Mon, Jan 19, 2015 at 8:51 AM, Cyd Haselton wrote:
>> Hello,
>> I'm struggling with a build issue on Android; I've posted to the
>> general python list with no result, so I'm re-posting here in hopes
&
Hello,
I'm struggling with a build issue on Android; I've posted to the
general python list with no result, so I'm re-posting here in hopes
that someone can help. If this is the wrong place feel free to let me
know.
I'm attempting to build Python 2.7.8 on my Android device; I'm using
an environme
46 matches
Mail list logo
