build(make): silence nohup output in projppu checksums#117
Merged
Conversation
The async checksum lines used `nohup bash -c "...>file..." 2>&1 &`, so nohup's own stdout was a tty and it printed `nohup: ignoring input / appending to nohup.out` into the build log. Redirect nohup's output with the $(QEND) macro (>/dev/null 2>&1 in normal builds, empty under VERBOSE), matching the cgroups-v1 cleanup. The `nohup md5sum < IN > OUT 2>&1` lines are left as-is — they already redirect nohup's stdout to the checksum file, and $(QEND) would clobber it. Refs bigstack-oss/cubecos#1005 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Travis Wu <travis.wu@bigstack.co>
traviswu-bigstack
added a commit
to bigstack-oss/cubecos
that referenced
this pull request
Jun 25, 2026
The api/ui/keycloak/appctl SOURCES rule listed $(RPMBUILD_DIR) as a normal prerequisite, but the rule writes rpmbuild/SOURCES.tgz into that directory, bumping its mtime on every build -> SOURCES is remade each run -> RPMS -> rpm -> heavy_rootfs -> rootfs.cgz -> pkg -> initramfs/cgz, so a no-change rebuild redid the whole tail. Make RPMBUILD_DIR an order-only prerequisite so its mtime no longer triggers a rebuild. Also in these files: - write version/build_number with `>` not `>>` (>> doubled the file on a rebuild, e.g. v3.1.0v3.1.0, corrupting the rpm filename). - ui/keycloak: touch $@ on SOURCES. - drop tab-indented recipe comments that make echoes into the build output. Bumps the hex submodule to the projppu nohup -> $(QEND) build-output cleanup (bigstack-oss/hex#117). hex#117 must be reviewed and merged first. Validated via remake jail + make pxe twice: pass 2 has no rpm/heavy_rootfs/cgz rebuilds and no echoed comments. Refs #1005 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Travis Wu <travis.wu@bigstack.co>
Eandalf-Bigstack
approved these changes
Jun 25, 2026
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
2 participants
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 this PR does
The async checksum lines in
make/projppu.mkusednohup bash -c "…>file…" 2>&1 &— so nohup's own stdout was a tty and it printednohup: ignoring input … appending output to 'nohup.out'into the build log.Redirect nohup's output with the
$(QEND)macro (>/dev/null 2>&1in normal builds,empty under
VERBOSE), matching the cgroups-v1 cleanup. Thenohup md5sum < IN > OUT 2>&1lines are left as-is — they already send nohup's stdoutto the checksum file, and
$(QEND)would clobber it.Validation
Part of the cubecos build-output cleanup validated via remake jail +
make pxetwice(bigstack-oss/cubecos#1007): the
nohup:message no longer appears in the build log.Linked issue
Refs bigstack-oss/cubecos#1005 (cross-repo; the build-incrementality + output-cleanup tracking bug).