yeti

Results 31 comments of yeti

I got commit 71ec7b86e5aaf17b6f99b88c09793f850c7ccf3a + llvm-r316129 + cfe-r316129 built on Debian9/amd64. Which newer combinations should work too?

> Looks like the latest commit here mentions svn id r318998. It does. But... Building 6380335 (current master) ``` HEAD is now at 6380335... Merged with upstream r318998. ``` against...

https://github.com/jacobly0/llvm-z80/blob/c90bdd4a58483b56bb5488674724ce62296ea6d5/tools/clang/lib/Driver/ToolChains/ZDS.cpp#L44-L45 I probably can only wave goodbye... no Windows here...

Maybe I can throw the *.s files in binutils-z80's assembler or the one of sdcc or z80asm... Somewhen later... I'll have a closer look at LLVM with some other backend...

Maybe setting ``` /*#define USB_CFG_SERIAL_NUMBER 'N', 'o', 'n', 'e' */ /*#define USB_CFG_SERIAL_NUMBER_LEN 0 */ ``` and trying to detect this in an own UDEV rule is safer. I don't know...

> but it looks like the ack driver doesn't have a way to pass that flag on to the linker --- that's worth having. I indeed looked into the man...

Maybe my results are related, even when caught on Debian and Raspbian. They patially overlap with the errors above. ``` $ git describe --always ae7656465 ``` On Debian9.9/amd64: ``` ****...

I installed ack into `/opt/ack` and ... $ printf "#define foo bar\nfoo\n" | /opt/ack/lib/ack/cpp.ansi # 1 "" # 2 "" bar ...looks like a `cpp` at work. I see no...

On the NodeMCU V1 (and its clones e.g. named "Amica") uploading works with the default settings. Which board are you using?