Giter Club home page Giter Club logo

lfs-notes's People

Contributors

pretorh avatar

Stargazers

avatar avatar

Watchers

avatar avatar avatar

lfs-notes's Issues

Tests: Create generic test parsing script 

grep -E '^(FAIL|UNSUPPORTED|XFAIL|XPASS): ' out.log
grep -E '^PASS: ' out.log | wc -l

# for each result type:
grep '^# TOTAL' out.log | awk -F: '{sum+=$2;} END{print sum;}'
grep '^# PASS' out.log | awk -F: '{sum+=$2;} END{print sum;}'
grep '^# SKIP' out.log | awk -F: '{sum+=$2;} END{print sum;}'
grep '^# FAIL' out.log | awk -F: '{sum+=$2;} END{print sum;}'
grep '^# ERROR' out.log | awk -F: '{sum+=$2;} END{print sum;}'

# what else is there?
grep '^# ' out.log | grep -v -E '^# (TOTAL|PASS|SKIP|FAIL|ERROR): '
grep 'expected passes' out.log
grep 'Tests=' out.log

cleanup: determine versions based on directory name, not via constants

some patch/post scripts need the path of a directory, based on the package's version. determine this from the working directory, instead of hardcoded (and needing to update on each update) in the scripts

ex scripts/6/6/systemd-patch.sh has SYSTEMD_VERSION=251, but can use something similar to scripts/6/perl-configure.sh to get the version number

consider splitting build and install of pre-chroot commands

build with the lfs user as in the notes, but install into a fakeroot only. install from this using sudo

this should remove the need to make lfs the owner of the root filesystem (and needing to fix that before entering chroot), and allow using package managers at this point already

Consider using symlinks for /bin, /lib

A lot of packages install bins and libraries into /usr/bin or /usr/lib, resulting in a lot of notes about moving them to the "correct directory"

Changing these to symlinks (/bin -> usr/bin, /lib -> usr/lib, /lib64 -> usr/lib) will probably simplify a lot of the post-install of packages (even if breaking FHS compliance)

Cleanup: remove BLFS package details (use summary instead)

BLFS will have a lot of packages to install. Adding a new file for each package will create a large number of files, each of which will need to be updated on new releases

Rather change the BLFS docs to show the list of "wanted" packages (not their dependencies) with a quick summary of non-trivial build/post-install-configuration needed for them

recheck 11.2

A lot of test failures.

  • Need to recheck the steps, might miss some setup in one of the earlier setups.
  • Running binutils with --jobs 1 seems better (though slow)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.