David Fang
David Fang
the libtool script configured on 10.7 also suffers the same issue, fixable with same workaround of manually fixing the SP2NL and NL2SP lines. Very irritating.
same issue on 10.9, apparently
Observation: this workaround is still needed on more modern Apple tools: ``` $ clang --version Apple LLVM version 8.1.0 (clang-802.0.42) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin ``` Symptom (during...
just noting that this problem still persists with: ``` build-triplet: x86_64-apple-darwin17.7.0 c++: Apple LLVM version 8.1.0 (clang-802.0.42) ```
I actually looked at this a few months ago, and started trying to make my forward declaration headers work with GNU libstdc++ and (clang) libc++, and it was a significant...
Somehow this message escaped my attention. Workaround is to replace these silly headers with the original header, like . Need to find time to modernize the codebase...
Some of them are already documented in hacknet's documentation.
Seems like what you really want is a channel-set command, to manually drive channels. Shouldn't have to source garbage values on a channel just to get it to a state...
So ``` # channel-source-args L 1 1 1 1 1 ``` should have clobbered the effect of ``` # channel-rsource L ``` but instead we see: ``` L : .e(init:0)...