Hi! > > The ffsb Makefile cannot cope with the fact that the configure is now > > called from the main configure and the files generated by it are > > stored in the out-of-tree build directory. It looks for them in the > > local directory and does something stupid. You can run configure by > > hand in the ffsb source directory which will workaround the problem. > > > > From the long term perspective we need to support both out-of-tree > > build and cross compilation (which is the reason configure is called > > from the main configure script in order to pass parameters passed to > > the main script). The easiest solution would be to rip out the ffsb > > build system and use the LTP one. > > > > My attempt with building out-of-tree with your suggested work-around > failed as well, now the ffsb complains about the "all" target...
Strange, it worked for me after doing out of tree configure and then configure in the ffsb directory... > Trying building in-tree instead and see whether that works better. > > A question though: Why do you see a need for supporting builds in-tree? > Can't we just concentrate on supporting out-of-tree and thereby cut > down on the test matrix? There are no technical obstacles to that but there are user expectations, 99% of software builds software in tree and being different is something that may hurt software adoption. -- Cyril Hrubis chru...@suse.cz ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
