> My advice: do not run docker. I think this is a setting in the Travis file. > Otherwise the number of indirections becomes a tad too large: > Travis may itself run in VMs -> which runs containers --> in which > your run QEMU .... > A few too many moving parts IMHO. > > So your goal is to limit the number of these and remove docker from > the equation.
Thanks for the advice. Unwrapping these layers is a good idea. But I think it's still helpful to know why tests fail on those architectures. I had another repo that tests strace with QEMU+schroot, although many QEMU segfaults are still present. > > As for the failure to build on various architectures, are you sure the > toolchain you use is compiled with support for these? It looks like it > from the Travis matrix though. I can confirm that "gcc-4.6" ( in wheezy docker ), "gcc-4.9" ( in jessie docker ) and "libc6-dev" are indeed installed within docker and are not from Travis's Trusty box. Please let me know if I'm mistaken. ( : Thanks Yunchih ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
