Matěj Cepl

That bug is supposed to be fixed in 10.2: ``` luamake@stitny (master)$ ninja -v -f ninja/linux.ninja [0/3] cd 3rd/bee.lua && ninja -f ninja/linux.ninja [2/2] build/linux/bin/bootstrap test/test.lua FAILED: build/linux/_/test build/linux/bin/bootstrap test/test.lua...

> @mcepl > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67791 Well, but that warning means that there is a bug in luamake (`Enable multithreading to use std::thread:`), doesn’t it?

It was enough to build luamake to: ```sh cd 3rd/bee.lua/ git checkout master git pull ninja -vvv -f ninja/linux.ninja .. ninja -vvv -f ninja/linux.ninja ```

Hmm, then I am not sure whether I have fixed it at all. Why do you need to import from a data directory anyway?

Hmm, it doesn't ... https://github.com/mcepl/pitz/blob/e26b27a3b9ed42d9284094a7fce2228424791b0e/test-log-pitzdir.txt I will work on it to fix those failures.

BTW, travis-CI build of this branch https://travis-ci.org/mcepl/pitz/builds/15131916

Could you instead help to bring m2r to mistune 2.0 API, please? I am the lead Python maintainer for openSUSE and mistune puts us between a rock and a hard...

> The [PR](https://github.com/miyakogi/m2r/pull/43/files) is waiting to be merged to fix this issue. Seems like this repository is not being maintained anymore. Fixing the issue should actually mean fixing the issue.

Just to confirm that even with m2r-0.2.1 and mistune-2.0.0 I get exactly the same result. [Complete build log](https://github.com/miyakogi/m2r/files/7675630/_log.txt) showing all packages used and steps taken to achieve the failed test.

> They have already have a [PR](https://github.com/CrossNox/m2r2/pull/43) on this issue and hopefully it will be released soon. And again, that PR is not fix just freezing old version of mistune.