search for: system_error

...cpp for Debug+Asserts build llvm[1]: Compiling Debug.cpp for Debug+Asserts build llvm[1]: Compiling DeltaAlgorithm.cpp for Debug+Asserts build llvm[1]: Compiling Disassembler.cpp for Debug+Asserts build In file included from CommandLine.cpp:25: /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:499: error: ‘EAFNOSUPPORT’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:500: error: ‘EADDRINUSE’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:501: error: ‘EADDRNOTAVAIL’ was not declare...

...-lstdc++ -lm -lpthread -lpthread -L/usr/local/google/home/blaikie/dev/llvm/build/clang/debug/split/notypes/nostandalone/./lib/clang/5.0.0/lib/linux -lclang_rt.xray-x86_64 -latomic -ldl -lrt /usr/local/google/home/blaikie/install/bin/../lib/gcc/x86_64-pc-linux-gnu/6.1.0/../../../../include/c++/6.1.0/system_error:197: error: undefined reference to 'std::_V2::generic_category()' /usr/local/google/home/blaikie/install/bin/../lib/gcc/x86_64-pc-linux-gnu/6.1.0/../../../../include/c++/6.1.0/system_error:197: error: undefined reference to 'std::_V2::generic_category()' /usr/local/google/home/blaik...

Hello, llvmdev! Subj, not all UNIX systems have that much number of errnos, so I'm attaching the workaround that i've used to build llvm. Hope this gets resolved. Thanks! -------------- next part -------------- diff --git a/include/llvm/System/system_error.h b/include/llvm/System/system_error.h index 3bfc092..2c0fa5c 100644 --- a/include/llvm/System/system_error.h +++ b/include/llvm/System/system_error.h @@ -470,6 +470,16 @@ template <> struct hash<std::error_code>; # endif #endif +#ifndef EBADMSG +# define EBADMSG 104 +#endif +#ifnde...

On Sat, 3 Jun 2017 16:04:57 -0700 Tim Northover <t.p.northover at gmail.com> wrote: [snip] > I think you should be able to fix it by changing the > compiler-rt/lib/xray/test/CMakeLists.txt. If you find the > "add_compiler_rt_test" call and move "-lstdc++" to the end, just after > "-lrt" it should work. Thanks, Tim. I don't see "-lrt":

...-L/home/hanzer/build/build_llvm/./lib/clang/4.0.0/lib/linux -lclang_rt.xray-fdr-x86_64 /home/hanzer/build/build_llvm/./lib/clang/4.0.0/lib/linux/libclang_rt.xray-fdr-x86_64.a(xray_buffer_queue.cc.o): In function `std::make_error_code(std::errc)': /opt/rh/devtoolset-6/root/usr/include/c++/6.2.1/system_error:197: undefined reference to `std::_V2::generic_category()' /home/hanzer/build/build_llvm/./lib/clang/4.0.0/lib/linux/libclang_rt.xray-fdr-x86_64.a(xray_buffer_queue.cc.o): In function `std::error_code::error_code()': /opt/rh/devtoolset-6/root/usr/include/c++/6.2.1/system_error:141: undefine...

...marks.a lib/libLLVMBitstreamReader.a lib/libLLVMMC.a lib/libLLVMBinaryFormat.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMSupport.a lib/libLLVMDemangle.a /usr/lib64/libz.so -lrt -ldl -ltinfo -lpthread -lm && : terminate called after throwing an instance of 'std::system_error' what(): Resource temporarily unavailable #0 0x00000000004d1244 PrintStackTraceSignalHandler(void*) (/home/usr4/c74014i/opt/clang/current/bin/ld.lld+0x4d1244) #1 0x00000000004cf1ee llvm::sys::RunSignalHandlers() (/home/usr4/c74014i/opt/clang/current/bin/ld.lld+0x4cf1ee) #2 0x00000000004d1...

...t;cstdio> > 1 #include <cstdlib> > 2 #include <cstring> > 1 #include <deque> > 2 #include <iterator> > 2 #include <limits> > 2 #include <memory> > 4 #include <mutex> > 1 #include <system_error> > 1 #include <thread> > 2 #include <tuple> > 1 #include <unordered_map> > 1 #include <unordered_set> > 3 #include <utility> > I think the biggest part is containers, and they are mostly > in ./xray_buffer_queue.h a...

...rect in assuming that this is actually "bad" code since it's a library function that writes directly to stderr? Yes, this is extremely unfriendly to using the linker as a library. It would be much better for the linker to return its error in a proper way (i.e. extending llvm/Support/system_error.h like llvm/Object/Error.h does). > Is the recommended approach to pass a stream to the constructor of any pass or function that wants to emit output outside of debug mode? My concern with this approach is that the compiler would then need to know which passes expect an output stream, and whic...

...<cstdlib> > > 2 #include <cstring> > > 1 #include <deque> > > 2 #include <iterator> > > 2 #include <limits> > > 2 #include <memory> > > 4 #include <mutex> > > 1 #include <system_error> > > 1 #include <thread> > > 2 #include <tuple> > > 1 #include <unordered_map> > > 1 #include <unordered_set> > > 3 #include <utility> > > I think the biggest part is containers, and they are mostly i...

...<cstdlib> > > 2 #include <cstring> > > 1 #include <deque> > > 2 #include <iterator> > > 2 #include <limits> > > 2 #include <memory> > > 4 #include <mutex> > > 1 #include <system_error> > > 1 #include <thread> > > 2 #include <tuple> > > 1 #include <unordered_map> > > 1 #include <unordered_set> > > 3 #include <utility> > > I think the biggest part is containers, and they are mostly i...

...nces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner > Subject: Re: [LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs() > It would be much better for the linker to return its error in a proper way > (i.e. extending llvm/Support/system_error.h like llvm/Object/Error.h does). > The right fix for this is to fix the code to not report errors textually. Unfortunately, the use of outs() and (especially) errs() is rampant - a simple grep of the 3.1 source tree shows about 1,500 instances. One of the first things we had to implement in...

...W, because of inline asm in valgrind.h that LLVM can't yet handle, I use: > > ac_cv_header_valgrind_valgrind_h=no .../configure ... when i do that i get: llvm[1]: Compiling regfree.c for Release+Asserts build llvm[1]: Compiling regstrlcpy.c for Release+Asserts build llvm[1]: Compiling system_error.cpp for Release+Asserts build llvm[1]: Building Release+Asserts Archive Library libLLVMSupport.a make[1]: *** [/home/rkotler/caviumllvmwclang/build/Release+Asserts/lib/libLLVMSupport.a] Error 127 make[1]: Leaving directory `/home/rkotler/caviumllvmwclang/build/lib/Support' make: *** [all] Error...

...gt;>> use: >>> >>> ac_cv_header_valgrind_valgrind_h=no .../configure ... >> when i do that i get: >> >> llvm[1]: Compiling regfree.c for Release+Asserts build >> llvm[1]: Compiling regstrlcpy.c for Release+Asserts build >> llvm[1]: Compiling system_error.cpp for Release+Asserts build >> llvm[1]: Building Release+Asserts Archive Library libLLVMSupport.a >> make[1]: *** >> [/home/rkotler/caviumllvmwclang/build/Release+Asserts/lib/libLLVMSupport.a] >> Error 127 >> make[1]: Leaving directory >> `/home/rkotler/caviuml...

Hi! These warnings and errors might be interesting to you when compiling rev. 116572 of llvm and clang on windows: \llvm\utils\killthedoctor\system_error.h(260) : error C2065: 'EAFNOSUPPORT' : undeclared identifier and many similar errors regarding the system error constants. msdn says it's WSAEAFNOSUPPORT instead of EAFNOSUPPORT (prepend WSA... to all system error constants) \llvm\tools\clang\lib\Serialization\ASTReaderStmt.cpp(1083)...

There are several libraries in LLVM that create their own `error_code` categories, so that they can return errors in a consistent way and with convenient messages. To do this, these libraries create an error category type that inherits from `_do_message` in system_error.h. There are a number of ways that this is wrong: 1. From the name, it's quite clear that _do_message is an implementation detail. 2. The only function defined in _do_message is specifically intended for system errors that report via errno, which is not what the custom categories are...

...; ac_cv_header_valgrind_valgrind_h=no .../configure ... >>>> when i do that i get: >>>> >>>> llvm[1]: Compiling regfree.c for Release+Asserts build >>>> llvm[1]: Compiling regstrlcpy.c for Release+Asserts build >>>> llvm[1]: Compiling system_error.cpp for Release+Asserts build >>>> llvm[1]: Building Release+Asserts Archive Library libLLVMSupport.a >>>> make[1]: *** >>>> >>>> [/home/rkotler/caviumllvmwclang/build/Release+Asserts/lib/libLLVMSupport.a] >>>> Error 127 >>>> m...

...-build$ ../llvm-src/configure --enable-optimized ~/llvm/llvm-build$ make llvm[1]: Compiling CommandLine.cpp for Release+Asserts build In file included from /home/svozniuk/llvm/llvm-src/lib/Support/CommandLine.cpp:25: /home/svozniuk/llvm/llvm-src/include/llvm/Support/system_error.h:499: error: ‘EAFNOSUPPORT’ was not declared in this scope /home/svozniuk/llvm/llvm-src/include/llvm/Support/system_error.h:500: error: ‘EADDRINUSE’ was not declared in this scope .........And another 50 errors of the same type follow......... 4. Install clang from Ubuntu reposit...

...du [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chris Lattner >> Subject: Re: [LLVMdev] [llvm-commits] [PATCH] Allow per-thread re-direction of outs()/errs() > >> It would be much better for the linker to return its error in a proper way >> (i.e. extending llvm/Support/system_error.h like llvm/Object/Error.h does). > >> The right fix for this is to fix the code to not report errors textually. > > Unfortunately, the use of outs() and (especially) errs() is rampant - a simple grep of the 3.1 source tree shows about 1,500 instances. One of the first things we h...

..._objects.dir/__/src/shared_mutex.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/stdexcept.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/string.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/strstream.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/system_error.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/thread.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/typeinfo.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/utility.cpp.o projects/libcxx/lib/CMakeFiles/cxx_objects.dir/__/src/valarray.cpp.o projects/libcxx/lib/...

...--enable-optimized > ~/llvm/llvm-build$ make > llvm[1]: Compiling CommandLine.cpp for Release+Asserts build > In file included from > /home/svozniuk/llvm/llvm-src/lib/Support/CommandLine.cpp:25: > > /home/svozniuk/llvm/llvm-src/include/llvm/Support/system_error.h:499: error: > ‘EAFNOSUPPORT’ was not declared in this scope > > /home/svozniuk/llvm/llvm-src/include/llvm/Support/system_error.h:500: error: > ‘EADDRINUSE’ was not declared in this scope > .........And another 50 errors of the same type follow......... > > >...