On Sat, 05 Jun 2010 11:17:23 +0100
Andrew Benton <[email protected]> wrote:

> On 05/06/10 09:43, littlebat wrote:
> > I am using Ubuntu 10.04 as the LFS building host. And I am learning LFS 
> > BOOK 6.6: 4.5. About SBUs: 
> > http://www.linuxfromscratch.org/lfs/view/6.6/chapter04/aboutsbus.html
> >
> > I am using a E7400 double cores CPU, I want set an environment variable 
> > with command provided by LFS book as below:
> >
> > <code>
> > set MAKEFLAGS='-j 2'
> > </code>
> >
> > I set it in either ~lfs/.bashrc or executed it under gnome terminal, but I 
> > can't get its value through<code>echo $MAKEFLAGS</code>. I thought it 
> > failed at setting this environment variable.
> >
> > I read the "help set" and did some searching on google and almost no use 
> > case about setting environment varible with "set" command except one I 
> > confirmed it can't work under my Ubuntu 10.04 host.
> >
> > I consider it is a LFS BOOK 6.6 bug, isn't it?
> >
> 
> It should be export MAKEFLAGS='-j 2' shouldn't it? Personally I have 
> never tried using the MAKEFLAGS variable because I have had problems 
> with glibc not installing correctly if make install is run with parallel 
> jobs. It compiles fine with make -j4 but I've learned to always run just 
> plain vanilla make install.
> 
> Andy
> -- 
> http://linuxfromscratch.org/mailman/listinfo/lfs-dev
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page

I have read the section following carefully : 4.5. About SBUs: 
http://www.linuxfromscratch.org/lfs/view/6.6/chapter04/aboutsbus.html

>From my understanding, LFS BOOK 6.6 is implicit to say we can always use 
>MAKEFLAGS='-j 2' or make -j2 to reduce compiling time when using a double 
>cores CPU. If we run into a problem with a build step, revert back to a single 
>processor build to properly analyze the error messages. 

How about my understanding of this issue?

-- 
littlebat <[email protected]>
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to