On Thursday 17 March 2016, Karel Zak wrote: > On Wed, Mar 16, 2016 at 04:27:10PM +0100, Ruediger Meier wrote: > > And we could disable setarch's uname26 test because > > # glibc requires kernel >= 3.0, thus setarch --uname-2.6 fails > > # on platforms without VDSO > > OK, added exception for sparc. I don't fully understand the real problem. See also this Debian package comment: "Apparently glibc does not support 2.6 personality on some architectures when built to require newer kernels (e.g. >= 3.2). See https://bugs.debian.org/806911"; Couldn't we tell setarch at build time that uname26 will not work with the used glibc? On openSUSE 13.2,arm7vl and on that debian,sparc machine we see this diff: Switching on STICKY_TIMEOUTS. Switching on ADDR_LIMIT_3GB. Switching on UNAME26. -success +FATAL: kernel too old Where does the "FATAL" message come from? Is it printed directly by glibc? If yes then we could use it to skip the test. (Allthough the kernel is not really too old but probably something is too new or just different.) But on openSUSE 13.2 arm6vl and aarch64 I don't get this last "FATAL" message but a segfault instead! Is there something we could do in setarch to avoid this segfault? (These arm6vl and aarch64 machines seem to run differently as "qemu_user_space_build"). BTW the test works fine on openSUSE 13.1 and 42.1. (newer and older than 13.2). cu, Rudi -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
