MicroPython Forum (Archive)

> rather than read between the lines

Forgot to mention - yes, that was the culprit.

pfalcon wrote:But I still don't get how you got from backslashes to NLR failure

Me neither. On unix it 'properly' segfaults.

So, the recommendation is to turnoff libffi on windows?

I believe I do have libffi installed on my cygwin environment. Still, I'm getting same error messages.

What's the main consequence of turning libffi off?

It builds under native Windows. I'm tried it with Windows 7/MinGW32. But I'm not using it a lot. Just to have it around.

igorgatis wrote:So, the recommendation is to turnoff libffi on windows?

I believe I do have libffi installed on my cygwin environment. Still, I'm getting same error messages.

What error messages exactly? The ones from the first post in this thread? And what compiler ae you using to build uPy?

Yes, same error messages. I'm using cygwin's gcc 5.2.0.

Hmm maybe I should update my cygwin installation then (I thought the setup.exe did it automatically?), mine is at version 4.9.3. In any case I'm having the same problem, x86 and x64 builds, yet according to setup.exe everything ffi-related is installed so I'm starting to think the cygwin ffi thing is just broken?

To answer your question: without ffi there's no uPy ffi module and parts of micropython-lib won't work as it uses ffi.

But micropython-lib doesn't have support for cygwin libc loading anyway (but it would be pretty easy to add, definitely much easier than for native Windows API).