Repository navigation
A build from scratch and a rebuild on a cached tree install the same programs - #427
Merged
Merged
Conversation
…programs libmnl is built before iproute2, whose libmnl tools are left out (ip and tc keep it for the kernel's error messages), and Python is built without its dbm modules, which only a cached tree holding gdbm gave it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was wrong. Stage 04 builds its steps in a fixed order, but some packages pick up an optional library only if it is already installed. A build from scratch, as a release tag's is, sees only the steps before it. A rebuild on a cached tree sees everything an earlier build installed. Two packages came out different:
devlink,rdma,tipc,dcb,vdpa,dpll,netshaper), plus anipthat prints the kernel's extended error messages._gdbmtoo.The program list (#403) was made from a cached tree's image. A build from scratch then failed stage 06 on eight entries naming nothing (Distro 38246073914). This is the trap perl's recipe already guards against for its GDBM_File module.
What changed.
ipandtcnow always build with libmnl, so a failedipcommand in the net zone's log says what the kernel refused, for example "Error: Nexthop has invalid gateway." instead of only "RTNETLINK answers: Invalid argument"._gdbmand_dbm(py_cv_module__gdbm=n/a,py_cv_module__dbm=n/a), and the recipe removes any copy a cached tree holds. Nothing importsdbm.gnuordbm.ndbm;dbmitself falls back todbm.dumb.How the run proves it.
ready-fold-09restores the first run's stage 04 tree and rebuilds from Python on, which is exactly the cached-tree case. Stage 06's program check then passes only if that rebuild installs neither the seven tools nor_gdbm.ipandnfton the result.Stacked on #348, whose lines in
python.shthis extends. Merge it with #403.