Naja, und weil die Stadt mit „K“ und ihren Doppelkirchtürmen ja auch ein Ticken größer ist als „D“ - hier nochmal eine Zugabe - der #Jupp von #BAP.
@briankrebs @tinker @catsalad @anagnostes @20002ist jupp users only drink coffee at home or where it’s reeeeally good (like Haferkater) and aren’t averse to an occasional tea or çay. They avoid Starbucks like a plague, it’s disgusting. ed(1) is the standard text editor.
@lanodan @cliffle yeah definitely, mirtoconf (“mksh/Build.sh”) by design outputs all of stderr so the build log captures them.
In Debian, I sed(1) a bit around so the build log checker doesn’t pick up warnings/errors from failed configure tests, though, but they’re still easily recognisable:
# Debian #492377, #572252
buildmeat() {
rm -f buildmeat.tmp
(set -x; env "$@"; echo $? >buildmeat.tmp) 2>&1 | sed --posix \
-e 's!conftest.c:\([0-9]*\(:[0-9]*\)*\): error:!cE(\1) -!g' \
-e 's!conftest.c:\([0-9]*\(:[0-9]*\)*\): warning:!cW(\1) -!g' \
-e 's!conftest.c:\([0-9]*\(:[0-9]*\)*\): note:!cN(\1) -!g' \
test -s buildmeat.tmp || return 255
return $(cat buildmeat.tmp)
}
Called as buildmeat sh Build.sh … then. mirtoconf only uses conftest.c which is not used elsehow in #mksh (or the other projects using it now, namely #pax, #sleep and in the future #jupp), so this works.