[Pkg-javascript-devel] Bug#1153699: wabt: remove unused re2c build dependency

haoran wang w1851687 at gmail.com
Wed Nov 11 05:58:32 GMT 2026


Package: src:wabt
Version: 1.0.42+dfsg+~cs1.0.39-2
Severity: minor
Tags: patch

Dear Debian JavaScript Maintainers,

Please consider removing re2c from wabt's Build-Depends. CMake compiles
src/wast-lexer.cc directly, and the source package contains no re2c
inputs, tool detection, or generation rules. The checked-in keyword table
is regenerated with gperf via the upstream update-gperf target.

In a controlled rebuild of the version above, re2c was removed from the
build environment and was not pulled back in by another dependency.
The native and Emscripten builds both completed, the results of all
137 tests matched the baseline, and the installed package payloads
were byte-for-byte identical.

The attached patch drops the re2c entry from debian/control.
The accompanying build-comparison.txt summarizes the baseline and the
rebuild without re2c.

Thanks,
Haoran Wang
-------------- next part --------------
A non-text attachment was scrubbed...
Name: remove-re2c.patch
Type: application/octet-stream
Size: 237 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20261111/636ce21b/attachment.obj>
-------------- next part --------------
wabt: build comparison after removing re2c

Source version: 1.0.42+dfsg+~cs1.0.39-2
Build architecture: amd64
Experiment: 92cfb6068dd4dca9, baseline vs. ablation-1

Check                       Baseline              Without re2c
re2c package                Installed             Absent, not pulled back in
Native CMake build          Completed             Completed
Emscripten/Ninja build      Completed             Completed
Named tests                 137                   137, results matched
Build log lines             3560                  3560
Build semantic summary      569 lines             569 lines
Installed package payloads  Reference             Byte-for-byte identical

Both runs compiled the same C++ lexer sources. The differences in the
compared compilation commands were Ninja step numbering and execution
order. The build logs were compared semantically.

The source package contains no re2c inputs, tool detection, or generation
rules. CMake compiles src/wast-lexer.cc directly. The checked-in keyword
table is maintained with gperf through the upstream update-gperf target.

These results are from the archived single-dependency removal experiment
for the version and build paths listed above.


More information about the Pkg-javascript-devel mailing list