Stability and debugging

Robert Connolly robert at linuxfromscratch.org
Sat Jul 22 13:48:46 PDT 2006


On July 22, 2006 03:56 pm, Declan Moriarty wrote:
> These sort of results question the whole business of compiling from
> scratch. I have gathered this much
>
> 1. Compiling new versions (particularly gcc-4.1x) the way LFS does it is
> somewhere between a major PITA and impossible.
I'm not sure what you mean by this. From what I can see gcc-4.1 a drop in 
replacement for the gcc-4.0 compiler already in lfs-svn, except with newer 
dependencies.

> 2. I sense a lessening confidence in the quality of the toolchain among
> the guys who should know here and that frankly undermines the whole
> system.
Again, I don't know what you mean by this. The gcc's keep getting better, more 
strict, and have better options.

> 3. The predictability of results on the range lfs ideally wants to cover
> ix86 32bit & 64 bit, amd & intel, and ideally ppc, sparc, etc. is
> lessening with advances in complexity. Introducing valgrind will add
> noticeably to times. 200 SBUs is enough to frighten anyone off.
The valgrind tests are intended for gcc developers, not really for the 
majority of people. Someone who modifies gcc would fall under "gcc 
developer".

> Others with deeper knowhow could no doubt add to this.
>
> Given the above, is there not a strong argument for this approach:
> Alter the content of a release. Make it a book and the appropiate
> tarball containing a prebuilt toolchain.
>
> The process would then be one of either
> 	1. Build your own toolchain with slightly different options if you were
> going somewhere odd with your particular system or
> 	2. Use the tarball as the final toolchain, and build the system
> Valgrind could then be compiled once, and then distributed.  There would
> be no need for a static build, the educational function of which is near
> zero anyhow. Anyone who deviates one iota from the book in chapter 5 is
> screwed, so the whole idea of compiling 'for choice of options' is gone.
There are ways to modify chapter 5. NLS can be disabled. Elfutils could be 
used to replace Binutils. You can leave out ncurses and texinfo. And with 
hlfs you can chose to enable one security option and not another.

robert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.linuxfromscratch.org/pipermail/hlfs-dev/attachments/20060722/af97597f/attachment.sig>


More information about the hlfs-dev mailing list