I do not see any problem, although why do we keep the disabled tests in this state?
These are NaCl's built-in tests which are built/run at compile time. They deal with stuff we don't use anymore or have overwritten and libc generates warnings about them. We're just going to disable these this way instead of futzing with the build process much while getting rid of the warning overload.
These are NaCl's built-in tests which are built/run at compile time. They deal with stuff we don't use anymore or have overwritten and libc generates warnings about them. We're just going to disable these this way instead of futzing with the build process much while getting rid of the warning overload.