Mark Rosenstand wrote:
> On Fri, 2009-09-18 at 00:20 +0000, Greg Schafer wrote:
>> (Sidenote: Any plans for LFS to incorporate parallel make into the build?
>> Seems like a gaping omission in this day and age of commonplace multicore
>> cpu's. At the very minimum, Glibc, GCC and Binutils should be given the
>> option of `make -jX' with the appropriate explanation...)
>
> Much more clever would be to mention MAKEFLAGS in the intro somewhere,
> and add -j1 as needed for the packages that don't support parallel make.
> This is what I do in my build scripts, and out of >1300 source packages,
> I've only had to enforce -j1 for 15 or so. Many of those are using
> obscure build systems, e.g. cdrtools with its Silly Makefile System.
I like that idea. It would seem to fit into Section 5.3. General
Compilation Instructions, perhaps as a subsection. We might also
consider using the environment variable CONFIG_SITE to cache configure
settings. E.g.
export CONFIG_SITE=/home/lfs/config.site
# /home/lfs/config.site for configure
# Give Autoconf 2.x generated configure scripts a shared default
# cache file for feature test results, architecture-specific.
if test "$cache_file" = /dev/null; then
cache_file="$prefix/var/config.cache"
# A cache file is only valid for one C compiler.
CC=gcc
fi
But I haven't really tried it.
Would you care to offer the wording to use? I think we are too close to
LFS 6.6 ut use this, but we might want to try it for 6.7.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
