Tim Rühsen

BTW, I now see memory leaks in curl - any interest in reporting those ? Or it that expected behavior ?

NP [make2.log](https://github.com/curl/curl-fuzzer/files/2410531/make2.log)

Yes I did. I can tell you that the broken build didn't generate libstandaloneengine.a at all. You can see that in `make.log`, it just wasn't built. I now revert to...

If I replace in Makefile.am ``` -LIB_FUZZING_ENGINE ?= libstandaloneengine.a +LIB_FUZZING_ENGINE = libstandaloneengine.a ``` then `autoreconf && make` works. Also `make distclean && ./mainline.sh` then works. Reverting the above brings back...

As a PoC, I changed `LIB_FUZZING_ENGINE`into `LIB_FUZZING_ENGINE2`. Same issue, so nothing from my environment.

If not setting `LIB_FUZZING_ENGINE` works for you but not for me, it looks like a regression in GNU make. Of course there are work-arounds as you say... but still it...

Same issue on Debian unstable. ``` $ java --version openjdk 11.0.3 2019-04-16 OpenJDK Runtime Environment (build 11.0.3+4-Debian-1) OpenJDK 64-Bit Server VM (build 11.0.3+4-Debian-1, mixed mode, sharing) ```

@robinvanleeuwen I could work-around the issue with `update-alternatives --config java` and then selecting the version 8.

@brunommarques Which version of wget2 do you use? (wget2 --version)

`2.1.0` is the latest release 🤔 Anyway, can you provide the full command line that lead to the situation? So that I can reproduce it.