On Fri, May 13, 2005 at 10:18:49AM -0400, Jeremy Huntwork wrote:
>
> But does this obscure information from the reader?
Not if properly explained in the beginning. Note that --prefix=/usr
isn't explained everytime, so the value of host, target, flags, whatever
needn't be explained everytime. And
On Fri, 13 May 2005, Jim Gifford wrote:
> Ken that's one of the things we are going to do after we get the builds
> working is go through every page and add more text or less text to give
> the reader a better understanding. We would welcome your input on this.
>
I'll be happy to contribute, but
Ken that's one of the things we are going to do after we get the builds
working is go through every page and add more text or less text to give
the reader a better understanding. We would welcome your input on this.
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux U
On Fri, 13 May 2005, Jeremy Huntwork wrote:
> Ken Moffat wrote:
> > In my opinion, put it all in variables - the sparc page has '-m32'
> > exposed to the reader without an explanation (although it might be
> > explained on another page). Put it all in variables, and explain them
> > at the begin
Ken Moffat wrote:
On Fri, 13 May 2005, Jeremy Huntwork wrote:
One nit-pick: you are using LFS_TARGET and LFS_HOST, why not just
TARGET and HOST ?
This one was done by me, there was a report of a distro having TARGET
and HOST set, I know we could just
override these variables. But I decided t
Ken Moffat wrote:
In my opinion, put it all in variables - the sparc page has '-m32'
exposed to the reader without an explanation (although it might be
explained on another page). Put it all in variables, and explain them
at the beginning, then just use them.
The explanatory text for the cross-lf
On Fri, 13 May 2005, Jeremy Huntwork wrote:
>
> Notice the use of $(BUILD32) in the x86_64 book that would contain (at
> least) the -m32 tag appended to the CC variable. It was thought that if
> we could have the user define the gcc tags needed to build for 32 or 64
> in the book for each arch, we
