Hi,
On Wed, 2009-02-04 at 13:32 +0900, Seiichi Ikarashi wrote: > >> Shouldn't this be removed from the build (via the Makefiles / > >> autoconf) because it doesn't apply for tcore based non-AMD chips or > >> did I goof up the support? > > > > I agree it's better to remove it from the build, but I don't know how to do > > it. > > Had a second thought. > I think it depends on the policy of LTP. This is a tricky thing to handle and both the approaches has it´s own pros and cons. And both of them are followed in LTP depending on the problem. > Two options can exist for unsupported case of tests. > (a) No build: Number of runnable tests varies on the systems (archs and > kernel versions). The recent introduction of AUTOCONF/AUTOMAKE supports the tests that fall in this category. These are those tests which cannot be built in the first place itself, as the pre-requisites of some header file/library is not present on the system. This is absolutely required to avoid unnecessary build failures on incompatible systems. But, this threw us one problem which we are still to solve completely. No build means no install as well. So, if this test(s) is/are of default LTP run, then PAN reports execve() failure of the same test(s), as thier entries are present in their respective command files, yet the binaries themselves are not present in $LTPROOT/testcases/bin. And we need to address this problem soon. > (b) Build: Test results can be one of pass, fail, and unsupported/unavailable. > This approach is needed in situations where the build/install process can happen, and a check can be done withing the parameters of test code, whether the support for such test is made available either through the architecture or through the kernel. I would prefer to keep them like them. So, for me both the approaches are necessary. Regards-- Subrata > Which is true for LTP? > > Regards, > Seiichi > > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code to > build responsive, highly engaging applications that combine the power of local > resources and data with the reach of the web. Download the Adobe AIR SDK and > Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > Ltp-list mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ltp-list ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
