-
-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
busybox build does not reproduce #1636
Comments
@JonathonHall-Purism some top of the head insight. modukes/busybox is actually the only one being rebuilt without caring of its .build status from global Makefile rules, bypassing them. I wonder if this is not the root of the problem, considering that CI rebuilds it multiple times depending of where that board is in the chain of workspace cache transfers. I think a little rework on modules/busybox (oldest Heads module?) refreshed and respecting proper build recipes could probably resolve the problem altogether with a little bit of investigation. Some timestamps get into that module build.
Which spams console on every local rebuild when only bash/ash scripts changed. This should vanish, and at the same time, this issue. |
I compared a CI build of #1630 with my local build, the only remaining reproducibility issue is busybox. All coreboot stages now reproduce, payload differs in the initrd only.
diffoscope identifies busybox. There are a lot of differences in disassembly and relocations but I think they all stem from a difference in string data (which causes more layout differences, etc.):
Some date format string changed slightly, now starts with
@@@
.NO NAME
also moved.(left is CI, right is my local build, and I did a clean build by deleting build/x86 and install/x86 for this)
The text was updated successfully, but these errors were encountered: