I've tested on Ubuntu Xenial now, and `ninja -t browse <target>` works fine there. Xenial has a newer version of ninja-build though (1.5.1-0.1ubuntu1), but I have to admit I don't know whether this bug is in ninja itself or the python web server it attempts to start.
Thanks for adding the requested information.
I've tested on Ubuntu Xenial now, and `ninja -t browse <target>` works fine there. Xenial has a newer version of ninja-build though (1.5.1-0.1ubuntu1), but I have to admit I don't know whether this bug is in ninja itself or the python web server it attempts to start.