SamyGO

I realized that my cross-compiled python not get ssl support. I need to recompile with openssl.
My TV is: UE32F5500

Which is the right toolchain for my TV i need to use to get ssl support.

I used arm-2012.09-64-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 to compile python.

@Murdock
Read topic with my first cross-compilation
I based on knowledge @juuso user (topic).

I read your topic before, but now i'm sure to use VDLinux-arm-v7a15v3r1.
Thanks!

Personally I'm using the arm-none-linux-gnueabi. At the instigation @zoelechat. Since I use it I haven't problem with cross-compilation for F-series. The cross-compile apps works also E and H series.

I also used "VDLinux-arm-v7a15v3r1" for f7000 and it work
https://forum.samygo.tv/viewtopic.php?f ... 0&start=30

Dear wluczykijwf or matrixabc!

Hello Again!

I compiled openssl with the help of the topic. I have the libssl.so and libcrypto.so file.
But i got warning that say openssl not compiled with "shared" instead pretend "no-shared". (Tried on Ubuntu, Kali, CentOs. All the same warning.)

Then i tried to compile python with ssl.

The "make python Parser/pgen" give me error in _ssl.c that say: no sslv2 and sslv3 find and then halt.

So, i commented out the lines that referenced to sslv2 and sslv3.
Now python was compiled. I need to copy the libss.so and libcrypto.so to python's lib directory manually. Now ssl is working.

But, I think this is not the right way to do this. Am i right?

Anomaly: When i telnet to the TV and start my server program in shell as usual with my python ssl version as background thread, i can access shell and run any command i want but i can't exit from shell anymore.

Murdock wrote: [...] But,(a very big but) I think this is not the right way to do this. Am i right?

I think that a size hasn't matter. A problem may be only with a free space in the /mnt directory.