NightStrike wrote: > I was hoping for something like "--disable-all --enable-ls" or some > such thing passed to configure to only run the configure tests for > the pieces of coreutils that I want to build.
Coreutils uses gnulib. Both coreutils and gnulib uses configure. So pretty much everything is connected and everything needs all of configure to run to completion. Then all of gnulib needs to build. At that point you can build a single executable. But by that point almost everything is building anyway. > That way, the configure tests that fail won't affect me. > > To be even more precise, I want to see how many of the core utils I > can get to natively compile for x86_64-pc-mingw32 using the new > compiler I just built. I think that you should be able to override the configure tests for things that are not working. Some useful information may be available in instructions for cross compiling. Usually what I have done is simply to read through and understand the configure tests that are failing and at that point the variables that need to be set are revealed. Then hack on the config.h file as needed. It is a blunt approach but as they say, brute force and ignorance will always triumph over elegance and finesse. Bob _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
