[tor-relays] Compiling tor-0.2.5.3-alpha on Raspberry Pi

[Oliver Baumann]

On 04/24/14, Lance Hathaway wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Apologies if this would be better addressed in a different list...
> 
> I know there are a couple of people here who are working on making the
> Raspberry Pi a good option for running Tor--and the work is
> appreciated! Gordon Morehouse has built binary pickages for the Pi,
> but I wanted to try compiling it myself (for good practice, mostly).
> 
> I followed the directions for compiling from source on a Debian-based
> system, but the compile fails with the following:
> 
> config/parse_bridge_line:
>   FAIL ../src/test/test_config.c:373: a.b.c.d was supposed to fail,
> but it didn't.
>   FAIL ../src/test/test_config.c:374: assert(!bridge_line)
>   [parse_bridge_line FAILED]
> 
> ...some log lines skipped for brevity...
> 
> 1/201 TESTS FAILED. (1 skipped)
> make[1]: *** [test] Error 1
> make[1]: Leaving directory
> `/home/pi/debian-packages/tor-0.2.5.3-alpha/build'
> dh_auto_test: make -j1 test returned exit code 2
> make: *** [build] Error 29
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> debuild: fatal error at line 1357:
> dpkg-buildpackage -rfakeroot -D -us -uc failed
> 
> 
> I confess, I haven't the slightest clue what to do with this. Have I
> overlooked something stupid? I don't want to open a "bug" unless it's
> an honest-to-goodness bug (developers have better things to do with
> their time than chase down "bugs" which are actually "user errors"),
> but I don't have the knowledge to say whether this is a bug or not...
> 
> Any thoughts?
> 
>  -Lance
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
> 
> iQIcBAEBCgAGBQJTWW95AAoJEECmBqfoBgXnbVcQALl69M5KuGTfpUH/nsl6hxCu
> RwB+u5kothwRIPoJblHdEa7m00sWJxUc8HlHfczgjIYkC1gob+vgIDiMR6skAc2t
> RdSaCYuKWTh6RVTXUAb4UNd3GdvTu/QW/5NsUYDFlTT4QIxg7W2OEOirC4x9bNei
> gspV+TyOBdJbrTWmVoBFh8YPbpVeY1R5rwARjv7BOhkDCAle3N4vh+S3LvUNr3hk
> bUimllKSK7fht7bFyesiCrPB1wUxEazAwD7iIDCj6XmVRM57Wu9TV48RO+LLWEB5
> qdKuTvN4MyqFbCiuBQXWU5Ps+IEOwoLSVzkQDvtdXhA1WvQmt8gVavXlRlZ+vWIi
> bEnJFxLMTqcwmC7RRk5blKr73/fBllaEumTpV4TfO3wRDwCKvtKLum9Z6wyV6g8n
> iY1WoJIThAiN6UM/nohKiecwM/L5e0gwEbkIxYLiCDGwzR3/QAvU84dv4a3EvWcy
> ptVZgcSQ3B4g55FOlTSJTasBG/rkCIm0Kdi6D7qXAUdm+ylSn/9eMcealSBwk38F
> Cfm/5P0bMAaKyGugY9VvoMPku8rsQgcimuUY8jH+8WgUxlUcZoL0fYSZ9hiVZ+m4
> zW+MiA8Ct2MSzx5GNDDjdBYs7TqOE/MywkSIoxzgy/h0fhAaC3Vm5+NpkI8Z7MUD
> /1MdDUHCawEZk8KHt7ev
> =GIPd
> -----END PGP SIGNATURE-----
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Hi Lance,
the reason you are seeing this seems to be a failing software-test which ships
natively with tor. I'm not experienced enough to comment on the nature of this
behaviour, for what I see it might as well be a bug.

Anyway, on my RasPi running Raspbian I had no problems compiling
tor-0.2.5.3-alpha with this: debuild -rfakeroot -uc -us
Try it and maybe report back!

All the best,
baumanno
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20140425/b848a653/attachment.sig>