Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Missing <string> when using -m32 with x86-x64 clang
See original GitHub issueIf you use -m32 switch then clang cannot find <string> header.
Works with gcc, but fails with clang.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Missing <string> when using -m32 with x86-x64 clang #431
If you use -m32 switch then clang cannot find header. Works with gcc, but fails with clang.
Read more >m32 when computing the prefix for programs/runtime libs - LLVM
I was trying to use -DLLVM_ENABLE_RUNTIMES=compiler-rt on FreeBSD and this failed since the 32-bit build ended up linking against the 64-bit ...
Read more >c++ - replace inline assembly tailcall function epilogue with ...
This snippet goes at the bottom of a function (which can't inline, and must be compiled with ebp as a frame pointer, and...
Read more >Tips for golfing in x86/x64 machine code
Even returning in st0 with non-empty higher stack registers would ... Instead, just use the string instructions for the upward direction.
Read more >toolchain_build/toolchain_build_pnacl.py - native_client/src ...
Use of this source code is governed by a BSD-style license that can be. # found in the LICENSE file. ... PackageBuilder docstring...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Try adding
-stdlib=libc++- this will use clang’s built-in libc++ standard library instead of GCC’s. I’m not sure why this is required, but hopefully you don’t need to compare GCC’s string implementation.Fixed since clang 5