You are correct in that the test is done at "runtime", but of course this actually only happens once at "configure" time for the package, which means it is using the runtime characteristics of a specific archive build machine, and at the time only. The behavior just happens to currently appear relatively "consistent" so far given the subset of ARM hardware and the given release that is being actively supported, but this is certainly not guaranteed to remain so. Hence I do happen to agree this methodology is itself flawed in the case of ARM.
-- [armel] the ./H5detect test segfaults when built for armv7 https://bugs.launchpad.net/bugs/635199 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
