Given that sqlite3 compiles its whole source as one translation unit,
the optimizations tend to take longer and longer and sqlite3's build
time increases. Therefore I ask for supporting parallel builds. In my
tests, we can achieve a 40% reduction in build time.

Helmut

Hi Helmut,
 Thanks for your work. As noted previously, upstream doesn't recommend
the individual source files. Of course, in Debian we use sources like
those that exist in the VCS repository for easy tracking of changes.
Upstream even says using / creating an amalgamation is how SQLite3
should be compiled to let the compiler choose the best optimization
techniques. That way the execution step can be increased by 5% to 10%
[1]. Compilation time however happens only once.
Once I already used parallel building and as I remember, not every
time but often enough it just broke. Can do testing locally and if
someone can help (donate) me old / small architectures - RISC-V for
example -, then I plan to re-test parallel compilation.

Regards,
Laszlo/GCS
[1] https://www.sqlite.org/howtocompile.html

I see debian/rules is using the build flag —disable-amalgamation. It used to be needed to build with option ENABLE_UPDATE_DELETE_LIMIT but that seems to be no longer true.

I think this build flag should probably be removed to get the speedups mentioned.