Opened 19 years ago

Closed 19 years ago

#1638 closed enhancement (fixed)

Make requirement to delete gcc source directory prior to final build more explizit

Reported by: felix.krull@… Owned by: lfs-book@…
Priority: lowest Milestone:
Component: Book Version: 6.1
Severity: minor Keywords:
Cc:

Description

Although LFS 6.1. states generally in chapter 5.1.:

"After installing each package, delete its source and build directories, unless specifically instructed otherwise."

  • this is most probabably not alway adhered to by the common LFS user - people

tend tp "rationalize" their work ;)

If one procede with the final GCC build in chapter 6.14 without deleting the source directory (and therefor without undoing the gcc-specs patch from chapter 5) - the build fails due to missing header files (stdio.h etc.).

That quite a number of people (including myself) have been hit by this scenario, is nicely documented in Google: http://www.google.de/search?q=tsystem.h+stdio.h+%22no+such+file+or+directory%22+LFS&

Therefore my suggestion: make the requirement to delete build/source directories between the different build stages more prominent or state the requirement explicitly again in the chapter for the final gcc-build.

Keep up the good work & best regards.h

Change History (2)

comment:1 by chris@…, 19 years ago

I don't think there is any need to add an additional note in the gcc-installation section or anywhere else. I also don't think there is a need to change what's in 5.1, but if it is changed then the paragraph about deleting source and build directories can be turned into an "important" note. In fact, it can be put into the same "important" note that's already in that section, about how all package installations assume you are already in that package's source directory.

The exact wording could also be modified - it mentions that deleting source directories "saves space", which I'm sure causes a lot of people to assume that deleting the source dirs is optional if you have a lot of available space.

comment:2 by Matthew Burgess, 19 years ago

Resolution: fixed
Status: newclosed

Felix, I've "fixed" this by placing more emphasis on the existing paragraph in chapter 5's introduction. User's have to take responsibility for ensuring they follow the book properly, so we don't want to hand-hold them too much.

by repeating the warning at various places throughout the book.

Chris, thanks for your suggestions, both of which were applied.

Note: See TracTickets for help on using tickets.