similar to: Disk space and RAM requirements in docs

Hi, I have a centos 5.6 xen vps which loses network connectivity once in a while with following error. ========================================= -bash-3.2# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available

Hi, I have a centos 5.6 xen vps which loses network connectivity once in a while with following error. ========================================= -bash-3.2# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available

Hi, I am trying to build the LLVM suite on a RedHat Enterprise Linux clone (Scientific Linux <https://www.scientificlinux.org/>). In the latest attempt, the build seems to complete without any explicit failures but the `check-all` process fails. Any ideas about what is wrong or suggestions for how to proceed would be much appreciated. This is the current procedure: sudo yum install

On Tue, Dec 10, 2013 at 3:57 PM, Reid Kleckner <rnk at google.com> wrote: > On Tue, Dec 10, 2013 at 11:58 AM, Hans Wennborg <hans at chromium.org> wrote: >> >> It would be nice if we could make the TypePrinter not print the >> calling convention if it's the default one for the ABI, but >> TypePrinter doesn't have a lot of context.. no Sema, no

On Tue, Dec 10, 2013 at 4:39 PM, Reid Kleckner <rnk at google.com> wrote: > I think we need to relax the test cases. MSVC usually prints the calling > convention, and it's often useful information. I was going to argue that MSVC doesn't print them, but then I tried, and you're right - it does :) I'll start relaxing the tests then. > Maybe we can make the

I think we need to relax the test cases. MSVC usually prints the calling convention, and it's often useful information. Maybe we can make the diagnostic text smaller by using the __thiscall, __cdecl, __stdcall, etc keywords when printing types with LangOpts.MicrosoftExt, but it will require moving the attribute from after the identifier to before, which is exciting. On Tue, Dec 10, 2013 at

msbuild is is able to re-run cmake if a CMakeLists.txt changes. CMake adds a special project "ZERO_CHECK" that does this. However, I am not sure it runs when invoking on the individual projects instead of the solution. Try the cmake --build command, which should output the following: > cmake --build . --target opt CMake is re-running because

On Tue, Dec 10, 2013 at 5:08 PM, Hans Wennborg <hans at chromium.org> wrote: > On Tue, Dec 10, 2013 at 4:39 PM, Reid Kleckner <rnk at google.com> wrote: >> I think we need to relax the test cases. MSVC usually prints the calling >> convention, and it's often useful information. > > I was going to argue that MSVC doesn't print them, but then I tried, >

On Sun, Aug 5, 2018 at 5:49 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 7.0.0-rc1 was just tagged (from the branch at r338847). >> >> It's early in the release process, but I'd like to find out what the >> status is of the branch

*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built

Hi cschen, It seems that libunwind (the one included in libcxxabi) is mandatory at the moment. Use the second build command instead: $ CROSS_COMPILING=arm ENABLE_LIBUNWIND=1 ./scripts/compile-all.sh Logan On Tue, Oct 7, 2014 at 5:32 PM, gamma_chen <gamma_chen at yahoo.com.tw> wrote: > After do "sudo apt-get update", the following are pass. > > Install the

Hi Ioannis, Just delete the projects/libcxx directory, then rebuild from scratch. You should only need to checkout llvm (in the top level directory) and cfe (into the tools/clang subdirectory). -Dimitry > On 29 Mar 2016, at 00:08, Ioannis Koukoulis <i.g.koukoulis at gmail.com> wrote: > > Hi Dimitry, > > I do not particularly need to build libc++ from the package. Is the

Hi Dimitry, this definitely worked. I am passed by the linking errors regarding libc++ or similar. My build stopped now at 95% while linking a clang extra, I am not pretty sure which because i do not have my laptop, possible the clang-rename, if such exists. No undefined references here, however, my hdd's free space run out, so this might be the cause. I have to move or expand now, alas!! The

Hello,    I get the following error while trying to configure an llvm build on Solaris 10-SPARC: CMake Error at projects/libcxx/CMakeLists.txt:268 (message):   C++11 is required but the compiler does not support -std=c++11 However, the error is about a missing header file (llvm/Support/Solaris.h) as reported in build/CMakeFiles/CMakeError.log: Performing C++ SOURCE FILE Test

Hi Dimitry, I do not particularly need to build libc++ from the package. Is the name of the package's libc++, libcxx, because this is where the installation starts finding undefined references, during linking CXX shared library ../../../lib/libc++.so. Please check below the first part of the log when the first error appear, I omited repeating results. Furthermore, the undefined references are

Try as I might I can't seem to get LLVM to bulid using clang/clang++. No matter what I do it insists on using /usr/bin/cc and /usr/bin/c++ which are gcc. Am I missing something obvious? I vaguely remember some document describing a stage1 compiler built by your old toolchain and a stage2 compiler but I can't find the steps to do that any more. $ CC=/usr/local/bin/clang

OK try it now - I checked in a few more fixes. On Tue, Feb 22, 2011 at 8:29 AM, Chuck Zhao <czhao at eecg.toronto.edu> wrote: > I still can't build LLBrowse on my Debian5-i386 machine today, > The following is a full build console output. > I am using LLVM-2.8 release build, with needed wxWidgets and CMake. > > Thank you > > Chuck > > sideshow.eecg>time

I still can't build LLBrowse on my Debian5-i386 machine today, The following is a full build console output. I am using LLVM-2.8 release build, with needed wxWidgets and CMake. Thank you Chuck sideshow.eecg>time cmake ../llbrowse -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /steffan/a/a0/czhao/bin/bin32/gcc -- Check

W dniu 2019-04-04 o 09:18, Tim Northover pisze: > On Wed, 3 Apr 2019 at 19:05, Audiovisart via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Does LLVM 8 work in macOS 10.9.5? > It should do. The released binaries appear to have been compiled so > they can run on that version, and Apple Clang 6.0 (from the newest > Xcode that runs on 10.9) meets the build

Here's the error: [ 58%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonNoTermination.iossim.dir/sanitizer_procmaps_mac.cc.o [ 58%] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonNoTermination.ios.dir/sanitizer_libc.cc.o [ 58%] Linking CXX shared library