Mon Oct 6 2025 Brian Inglis <[email protected]> wrote: > As gawk is a Cygwin Base category package, it should be one of the first > packages installed on all Cygwin systems, so the test should not be necessary, > unless /usr/bin is not in the PATH: a message to that effect might be more > useful; for example:
The issue appeared while cross-compiling on Debian. Tue Oct 7 2025 Jon Turney <[email protected]> wrote: > I wonder if it makes sense instead to check for this and other > prerequisite tools (e.g. perl) up front in the configure script? Generalizing error handling might be more useful. However, there is an issue with broken pipes on aarch64. This error handling might be applied once that issue is fixed. Thank you for the review. Regards, Evgeny diff --git a/winsup/cygwin/scripts/gentls_offsets b/winsup/cygwin/scripts/gentls_offsets index bf84dd0cb..67d0c02bd 100755 --- a/winsup/cygwin/scripts/gentls_offsets +++ b/winsup/cygwin/scripts/gentls_offsets @@ -4,14 +4,9 @@ input_file=$1 output_file=$2 tmp_file=/tmp/${output_file}.$$ +set -eo pipefail # fail if any command or pipeline fails trap "rm -f ${tmp_file}" 0 1 2 15 -# Check if gawk is available -if ! command -v gawk &> /dev/null; then - echo "$0: gawk not found." >&2 - exit 1 -fi - # Preprocess cygtls.h and filter out only the member lines from # class _cygtls to generate an input file for the cross compiler # to generate the member offsets for tlsoffsets-$(target_cpu).h.
