[ ijbswa-Feature Requests-3182820 ] Support for ARM on Android/Linux devices

Feature Requests item #3182820, was opened at 2011-02-15 13:53
Message generated for change (Comment added) made by fabiankeil
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=3182820&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Unix integration
Group: version 3.0
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
>Assigned to: Fabian Keil (fabiankeil)
Summary: Support for ARM on Android/Linux devices

Initial Comment:
Hi, I'm currently using Privoxy 3.0.12 on several rooted Android 2.2 devices (Nexus One, Galaxy S) - running Linux  Kernel 2.6.32.9. Privoxy is  working quite well for what I need - Thanks. 

However, I wanted to move to Privoxy 3.0.17. But, when I built and installed it, it Seg Faults. I could probably debug this further
but I'm wondering:

1. What are your current and future support plans for Linux 2.6+ kernel on ARM (Android) platforms? Will you support ARM or at least not disable it?
2. Will you be able to look at the 3.0.17 seg fault problem any time soon? Can you provide any  workarounds?

FYI: I will also have some code I'd like to contribute to Privoxy so I'm motivated to help make Android support happen.

Thanks.

John B. Hansen

P.S. I am cross-compiling Privoxy for ARM using Android 2.2 libraries (zlib) from December 2010.

----------------------------------------------------------------------

>Comment By: Fabian Keil (fabiankeil)
Date: 2012-11-23 11:23

Message:
I'm closing this as Privoxy seems to work fine on Android (it's part of
Orbot).

----------------------------------------------------------------------

Comment By: Yakov Kopel (kopely)
Date: 2011-03-05 23:36

Message:
try add:
//------------------------
#define MY_ANDROID_PROJ
#ifdef MY_ANDROID_PROJ
        typedef unsigned short in_port_t;
#endif
//------------------------
in project.h file header

----------------------------------------------------------------------

Comment By: Yakov Kopel (kopely)
Date: 2011-03-05 14:15

Message:
can u give more detailed guide,
about how to compile privoxy on android.
(even for the  3.0.12 version)
i didnt understend how did u do it?

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2011-02-16 13:46

Message:
Fabian, David, thanks for the quick replies.

FYI: I have tried disabling the IPv6code already using the technique you
mentioned and it didn't help.

I will work to provide you the stack trace and/or debug it myself. Stay
tuned on that.

Regarding the Android toolchain, I'm not able to run gdb yet but hope to be
able to do that soon i.e. once Android has a remote debug server method
that I understand. I use droid-wrapper to setup the environment variables
and cross-compile params and then build Privoxy in a subdir of my Android
build so it has access to zlib. The rest is pretty much the same except I
configure for cross-compile as follows:

>./configure --host=arm-none-linux-gnueabi

Thats about it for ARM support on an Android phone.

FYI: I'm not the only one using Privoxy on Android. I think Tor guys are
also using it.

Thanks.....jh

----------------------------------------------------------------------

Comment By: Fabian Keil (fabiankeil)
Date: 2011-02-15 14:53

Message:
I'm not aware of anything in Privoxy 3.0.17 that would make it incompatible
with ARM devices in general.

Privoxy's IPv6 code is known to trigger bugs in older versions of some
embedded libcs, though.

You could try the workaround for this, which is:

echo '#undef HAVE_RFC2553' >> config.h

followed by recompiling. Updating the libc would be the preferable
solution, though.

Of course this is just a wild guess and like David already mentioned, a
stack trace would be useful.

----------------------------------------------------------------------

Comment By: David Schmidt (david__schmidt)
Date: 2011-02-15 14:01

Message:
Platforms get support when interested developers add it in.  You're as
welcome to contribute patches the same as Amiga, OS/2, Windows, or anyone
else is.  Android sounds like fun to me.

Debug, though, is going to be up to you - do you have a stack trace?  I'm
not familiar with the toolchain - can you run gdb or whatever on a core
file and see where it crashed?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=3182820&group_id=11118

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov