On Tue, May 12 2020, Rafael Sadowski wrote:
> On Tue May 12, 2020 at 12:27:20PM +0200, Klemens Nanni wrote:
>> On Tue, May 12, 2020 at 07:09:42AM +0200, Rafael Sadowski wrote:
>> > I am working on a new cmake-python symbiosis. Python2 was detected in my
>> > last bulk. Looks like there is a typo i
On Tue, May 12, 2020 at 09:02:52PM +0200, Rafael Sadowski wrote:
> Yes and no. I saw the following lines in devel/llvm and thought I had
> caused it with my cmake changes. But this happens even without my
> changes, although we set MODPY_VERSION=${MODPY_DEFAULT_VERSION_3}.
Ah, good to know.
> -- C
On Tue May 12, 2020 at 12:27:20PM +0200, Klemens Nanni wrote:
> On Tue, May 12, 2020 at 07:09:42AM +0200, Rafael Sadowski wrote:
> > I am working on a new cmake-python symbiosis. Python2 was detected in my
> > last bulk. Looks like there is a typo in both Makefiles.
> These are no typos but valid m
On Tue, May 12, 2020 at 07:09:42AM +0200, Rafael Sadowski wrote:
> I am working on a new cmake-python symbiosis. Python2 was detected in my
> last bulk. Looks like there is a typo in both Makefiles.
These are no typos but valid make(1) syntax: it states that the
following command may fail.
Did yo
I am working on a new cmake-python symbiosis. Python2 was detected in my
last bulk. Looks like there is a typo in both Makefiles.
Rafael
diff --git a/devel/clang-tools-extra/Makefile b/devel/clang-tools-extra/Makefile
index dfebc54269f..664da0e7735 100644
--- a/devel/clang-tools-extra/Makefile
++
