Build order/dependency information

[chris@…]

LFS just rearranged the build order and added dependency information to a new appendix. The same should be done with CLFS. Most of the info should be the same, since most of the same packages are used, but there are likely to be some issues with CLFS, particularly with arch-specific packages. I would like to do the same as LFS - removing package dependency info from individual package installation pages and putting it all into a single Appendix. One possibility is to do the same thing as with the Materials (Packages and Patches) - have one page that's common to every system, then a second page with arch-specific stuff. Any one else have any thoughts on this?

[Jim Gifford]

Let's do it. We currently have a materials setup like that, but any changes you need to make let us know so we can help out.

[chris@…]

Here's what it would look like (except the dependency info would also be removed from each package installation page) - ​http://linuxfromscratch.org/~chris/cross-lfs-book/x86/ - unless of course anyone has any better ideas.

[chris@…]

Also, I only have x86 systems, so it would be great anyone with access to other archs can thoroughly test deps. for any other arch-specific packages (other bootloaders, elftoaout, hfsutils, dvhtool, etc.).

[Joe Ciccone]

Some sparc information

elftoaout - binutils gcc glibc make patch

/usr/share/man/man1/elftoaout.1	Man Page
/usr/bin/elftoaout	This program converts sparc elf binaries to a.out binaries.

The kernel can also use elftoaout, if you're building the vmlinux.aout target. If you're doing this you're probably planning on netbooting. the reason being that the sparc prom (OpenPROM) reads binaries in the a.out format. Silo uses elftoaout to convert the generated elf first stage loaders into a.out binaries.

silo - binutils coreutils elftoaout gawk gcc glibc grep gzip patch make sed

/etc/silo.conf	the silo config file.
/sbin/silo	the silo executable.
/usr/sbin/silocheck	checks to see wether a file is readable by silo. (very handy if you have larger disks.)
/usr/bin/maketilo	a tool for building a simple TFTP boot loader
/usr/bin/tilo	a tool for building a simple TFTP boot loader
/usr/share/man/man1/maketilo.1	Man Page
/usr/share/man/man1/tilo.1	Man Page
/usr/share/man/man8/silo.8	Man Page
/usr/share/man/man5/silo.conf.5	Man Page
/boot/fd.b	floppy disk first stage loader
/boot/first.b	first stage loader.
/boot/generic.b	first stage loader for v0, v2
/boot/ieee32.b	first stage loader for a javastation.
/boot/ultra.b	first stage loader for an ultra sparc.
/boot/second.b	second stage loader.
/boot/silotftp.b	second stage loader when booting from tftp.
/boot/isofs.b	the bootblock for a cd.

[manuel@…]

Chris, when doing the commit remember to update also the CSS code.

Or ask me to do it.

[chris@…]

Hmmm, I forgot about the css code...maybe you should do it since I don't know what would need to be changed. :)

[manuel@…]

OK.

After make the dependencies commit, please reassign this bug to me to know that the CSS code need be fixed.

[ken]

For ppc, dependencies are

hfsutils - bash, binutils, coreutils, gcc, make

parted - bash, binutils, coreutils, e2fsprogs [ that is, it links to libuuid.so.1 ], gcc, make, ncurses, readline

powerpc-utils - binutils, gcc, make, patch

yaboot - binutils, coreutils, gcc, make, patch, sed

Installed files should be correct in the book, except for parted:

/usr/sbin/parted - partition editor

/usr/sbin/partprobe - inform OS of partition table changes

[ken]

clarification for the ppc stuff - patch and sed are only dependencies because we use them explicitly in the book for the current versions of the packages

[chris@…]

I've just updated the dependency info for all archs and put it all into the Appendix, removed the dependency info from the individual package pages, and reordered all the temp-system sections. Here's what it looks like so far - ​http://linuxfromscratch.org/~chris/cross-lfs-book/. The only thing left to do is reorder the final-system packages and double-check dependencies for a few more packages (for any arch-specific package that wasn't checked so far, I just copied what was already listed in the book and put it into the Appendix). I think the final-system packages should be ordered the same as in LFS, with the exception of putting arch-specific packages and bootloaders last - does this sound like a good idea?

[chris@…]

Also, I need dependency info checked for mips and alpha packages.