Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ecb8226

Browse files
committed
PDF docs build: avoid spurious "warn" in build logs.
Improve on e4c8865 so that the string "warn" appears in the output when there's a problem, and not when there isn't. This should silence noise I've been seeing in my buildfarm warning scraper.
1 parent fb05656 commit ecb8226

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/Makefile

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -158,9 +158,9 @@ XSLTPROC_FO_FLAGS += --stringparam img.src.path '$(srcdir)/'
158158
# There is no easy way to pipe output and capture its return code,
159159
# so add a final line to report the return code.
160160
%.pdf: %.fo $(ALL_IMAGES)
161-
{ LANG=C $(FOP) -fo $< -pdf $@ 2>&1; echo "FOP_RETURN $$?"; } | \
161+
@ { LANG=C $(FOP) -fo $< -pdf $@ 2>&1; echo "FOP_RETURN $$?"; } | \
162162
$(AWK) 'BEGIN { warn = 0 } $$1 != "FOP_RETURN" { print } /not available in font/ { warn = 1 } \
163-
END { if (warn != 0) print("\nFound characters that cannot be output in the PDF document; see README.non-ASCII"); \
163+
END { if (warn != 0) print("\nWarning: found characters that cannot be output in the PDF document; see README.non-ASCII"); \
164164
if ($$2 != 0) { exit $$2} }' 1>&2
165165

166166

0 commit comments

Comments
 (0)