torbrowser
	-> see #10972
	Updated by intrigeri 7 days ago (10.02.2016)
	Comment

	  | | Do we have Tor Browser for arm?

	  | Kind of, you'll just have to build it yourself, see https://trac.torproject.org/projects/tor/ticket/12631

	  ... and without Gitian, if I got it right by merely skimming over the recent changes on that ticket.

	-> not built yet  

i2p
	-> built: libjbigi-jni_0.9.23-2~deb8u+1_armhf.deb
	-> not built:  
		i2p deb net optional arch=all
		i2p-doc deb doc optional arch=all
		i2p-router deb net optional arch=all
	-> while building i2p
	   debconf-updatepo
	   /build/qemu-1000/qemu-2.1+dfsg/tcg/tcg.c:1683: tcg fatal error
	   Segmentation fault
	   ==> seems to be the same as with grub2 (see below)
	-> no futher investigations yet

liveusb-creator
	-> failed, no futher investigations yet
	-> Message "no packages to build"

mesa
	-> build: 49 .dep packages
	-> no futher investigations if complete or correct

tails-greeter
	-> built: tails-greeter_0.8.18_all.deb
	-> no futher investigations if complete or correct

tails-installer
	-> failed, no futher investigations yet

tails-iuk
	-> failed, no futher investigations yet

tails-perl5lib
	-> failed, no futher investigations yet

tails-persistence-setup
	-> failed, no futher investigations yet

torbirdy
	-> built: xul-ext-torbirdy_0.1.4-1~d70.wheezy+1+tails1_all.deb
	-> no futher investigations if complete or correct

vidalia
	-> built: vidalia_0.2.21-5+tails1_armhf.deb
	-> installed on rpi 2 -> works!

whisperback
	-> failed, no futher investigations yet

window-picker-applet
	-> failed, no futher investigations yet

grub2
	-> failed, reason:

		/build/qemu-1000/qemu-2.1+dfsg/tcg/tcg.c:1683: tcg fatal error

		the orgigin crash message points to this code:
			
		#ifdef CONFIG_PROFILER
				s->del_op_count++;
		#endif

		--> Multithread issue, patch see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769983 and [2] http://patches.linaro.org/patch/32473/
--> seems that https://packages.debian.org/jessie/qemu has not fixed this problem ...

		The patch described in [2] must be applied
		to line 4410 (instead of 4334 as pointed in [2])
		in qemu-2.1.0/linux-user/syscall.c
		(the currently installed/used qemu-arm-static)

		Taken from [2]
			diff --git a/linux-user/syscall.c b/linux-user/syscall.c
			index 4823aa0..ff5ed06 100644
			--- a/linux-user/syscall.c
			+++ b/linux-user/syscall.c
			@@ -4334,6 +4334,15 @@  static int do_fork(CPUArchState *env, unsigned int flags, abi_ulong newsp,
				 if (nptl_flags & CLONE_SETTLS)
				     cpu_set_tls (new_env, newtls);

			+        /* agraf: Pin ourselves to a single CPU when running multi-threaded.
			+           This turned out to improve stability for me. */
			+        {
			+            cpu_set_t mask;
			+            CPU_ZERO(&mask);
			+            CPU_SET(0, &mask);
			+            sched_setaffinity(0, sizeof(mask), &mask);
			+        }
			+
				 /* Grab a mutex so that thread setup appears atomic.  */
				 pthread_mutex_lock(&clone_lock);

		--> no further resarch, if there's a more general fix at work or already published
		    (even if 

			" Running multi-threaded code can easily expose some of the fundamental
			  breakages in QEMU's design. It's just not a well supported scenario. "

		     it could take some time to be fixed properly ...)
		--> if not available applying quickfix and rebuild quemu-arm-static ...
		--> currently no idea if and how the build "performace" would be affected
		    by pinning to one single CPU ...