-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
could you two please comment on
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=628
and
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=644
what is needed to fix the issues?
Do we need remote access to armhf testing/build hardware, physical access, more debug logs, ...?
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUxfiSAAoJEG7d9BjNvlEZjugH/RAB38KMxMVQ5Ina6UbZZaXi 9UHUfgGKQwlSEJAFuXrB1c1XyNo9tWfsxHCwBiCyno2GnwGF7yL6QXbfPQwwGR43 FeQ2uiwzbfTqWnrE4m7jBcfTfMkiMBYgshnz6dOUEgg1eOdjP/131qbQHx+ydTrS 7Qlq5l8Wnw9hQ+/jxCOoQtu+vq3p2INaoJ2tbNvwC0NuYkmXaaMFnjOrmUNedlLa 0LzWQHaBeS4Hw6QK+04v25KUrRlggdC2LyvViEfg4VQP5fHOvNUT5KXzVC9PBmEv WxCAYM4ZtwOhRtq1jvSgDN2UNvdhq9RfreUqHkGGp/W2ZFzUo9XwFP3qcPs7ExU= =RXD/ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 26.01.2015 um 09:19 schrieb Stefan Baur:
PS: I don't want to promise anything yet, but from a recent off-list conversation, I think I might know somebody willing to sponsor some armhf hardware for us ...
And that is now confirmed. We can get at least 1 Raspi from a company that is interested in seeing regular builds on that platform. Please let me know where the machine should be going, i.e. if it would be best if one of the devs involved has physical access, or if I can just stick it next to the mac mini I'm currently hosting for X2Go.
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUxlU3AAoJEG7d9BjNvlEZQOcH+wVJ7zw52iT+S5s9zYBTpiY/ UHRnRXU/osXCUYquUhLC1WbIyxa6aVu08HPYxc+7dPkh7zKB8SUaTbZ/mBiFEAG7 DUV3EDKsOqksweQx4DDaZJXobtmlsh+/imRWmt37JhpJrDocPK2ZqkP9DCCDLe24 XUQE57rWtOOG7p7fhhExICwnRchugLbFCp/pw4FkIW8e13It+m5NigSsFmR8RjkG MeEwZ/nNhPTeJ81eiWHquXI4gq3nlfZZhwSvObWadAa1dVfvvu3BmUQBOjWpwJVF I51U/eOy7xZhKBfto89Fv9oU6ee0Zm0ucFarN9f3APGanh2hytTaJc0EP/KcVpY= =l8W/ -----END PGP SIGNATURE-----
On Mon, Jan 26, 2015 at 03:54:47PM +0100, Stefan Baur wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 26.01.2015 um 09:19 schrieb Stefan Baur:
PS: I don't want to promise anything yet, but from a recent off-list conversation, I think I might know somebody willing to sponsor some armhf hardware for us ...
And that is now confirmed. We can get at least 1 Raspi from a company that is interested in seeing regular builds on that platform. Please let me know where the machine should be going, i.e. if it would be best if one of the devs involved has physical access, or if I can just stick it next to the mac mini I'm currently hosting for X2Go.
- -Stefan
Hi,
for the client or the server or both?
Unfornatly the raspi is not compatible with the debian/ubuntu armhf binaries. Because of the vfp unit and the arm architecture. See https://wiki.debian.org/RaspberryPi
Bye Henning
-- tarent solutions GmbH Niederlassung Berlin Voltastraße 5, D-13355 Berlin • http://www.tarent.de/ Tel: +49 30 555785-0
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-0 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 26.01.2015 um 20:01 schrieb Henning Heinold:
[soon-to-be-expected Raspberry Pi hardware donation by sponsor]
for the client or the server or both?
The idea would be to either use it as a build host (Jenkins slave) or as a remotely accessible test/debug machine for X2GoClient.
Unfornatly the raspi is not compatible with the debian/ubuntu armhf binaries. Because of the vfp unit and the arm architecture. See https://wiki.debian.org/RaspberryPi
Could that be the reason why Franz failed to compile X2GoClient on Raspberry Pi in Bug #628? He filed the bug against <4.0.2.1-0x2go1+git20140823.626+wheezy.main.1> which would be plain Debian, not Raspbian, right? So maybe he was using the wrong source repo or pulled in armhf binaries from debian/ubuntu that are bount to fail on the Raspberry Pi?
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUxpDWAAoJEG7d9BjNvlEZd3UIAImjYBLHegGarPydhJNvPMxn eLIQ3qT9N2p7xPMb/hS1LdKiDQjVwRGCZUtoZdJWOlO4IZ9uuZNK1Q7oCXaixL1O 2x9z2OuS7gawmsgXIQ4WL+oNTFuSoqoCKHSIU5cIMyUkLefes0eYbRq3u/inbUN/ mrxjpO9Qh6icB2Qq4CYu8e6HcctnaedWLK0ueAwTThblkpAWRltpt6ngMfDsEPjQ eD/Jv3peyYc9mQI456BC4jRc04F9/Q6xmQGcq5p+IZnGKMtcPa0c70trD01weNT+ dA32hB25KkKOMMxI7+xmFxGzKRExChmDZ3Ssjk2TvqgugqP7o/z6EUo0PSFcQtI= =3XeX -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello Stefan,
Do we need remote access to armhf testing/build hardware, physical access, more debug logs, ...?
armhf does not uniquely specify an architecture as is described on https://wiki.debian.org/RaspberryPi and https://wiki.debian.org/ArmHardFloatPort .
Debian armhf requires an ARMv7 architecture. Rasbian armhf requires an ARMv6 architecture.
Arm can be emulated on an amd64 or x86 architecture. You might follow the instructions at http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation#For_Versati...
But this emulation is very slow. Hence it is recommendable to use native arm hardware for building and testing.
Unfortunately the mainline Linux kernel does not support all arm processors equally well. E.g. on an Allwinner A20 you can use only one out of two cores with Linux 3.19. One architecture that is sufficiently supported is Freescale i.MX6.
A single Wandboard Quad with a SSD drive should be enough do create nightly builds for all currently supported distributions. Hardware cost without 19" housing is below 200 EUR.
Cf. http://forums.wandboard.org/viewtopic.php?f=7&t=378
could you two please comment on
I added a comment recommending to close the issue.
and
The bug report lacks the necessary information to reproduce the problem. Comment posted.
Best regards
Heinrich Schuchardt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iQIcBAEBAgAGBQJUxpKLAAoJEMSB27wsBRrEdN8QAJhOCiIX8RSr0VrjSTtY26RZ Xt104kphCPiEXux8EQhAO8VZCjhfTbnDGnPRU76cuN5UnIC95PB3QkuYguSbntno Z5gsYfCan1WAZpHJWWzepykXHUnBA/Enz9y6BO6yzpUMN1Drp0qBIlkgOCqc9FF1 Bjbxi9TsNaAUms/HufkS143KyWntx9dL50okQq+w/PLa574E7wQn3BYRjVUbHXPp qlNOfTH22LC6uO8XtjguKiB6eE3L0gZefbZMJECp2Yyf8hesy9WP5OcfyJ6Luzbt aWb3f9+Mu0GoE8yKq9DGhcIpJvak58GVe5JPXaOY3gFE1x49aPI74jH8y1gTXCcD x5zNEB85gGsvPtKU19mbUe3ZJUYuIsFJGqRBil3W6J8uj+qLEf142GpRP8dTRONx Z4blgEf/ClzldGVXcnrY7AW8RxdOlTyLI2D853kmNa9mSNBW/nuCWaMrbkS3i3lR 3q3zNXoJLr3oYJ6WyA2Id/abK5/499rTrhiVS+0IcCZ4vFB/VeNyd2HdC+bCM2Gt TcrAQsMMWnRIBpxLzGjNnTF4Iju+8Mc9UAXGURPiv6J5YoL6jmgLoqWCdCJ7NPA3 wb+pof4h/Hrd+E45pp66EX2/Iz+audfB7o41D7tvqsei6RjTkfAVLapWxEx6O5yY HF+Xr1iVUWZcmG02VfTf =mcvz -----END PGP SIGNATURE-----