similar to: [LLVMdev] buildbot failure in LLVM on clang-native-mingw64-win7

This builder is taking too long to build. (The build stops because of a timeout.) Chip On Aug 30, 2013, at 11:29 AM, llvm.buildmaster at lab.llvm.org wrote: > The Buildbot has detected a new failure on builder clang-amd64-openbsd while building llvm. > Full details are available at: > http://lab.llvm.org:8011/builders/clang-amd64-openbsd/builds/1103 > > Buildbot URL:

git://git.zytor.com/users/genec/syslinux.git Branch win64-mingw32-ubuntu-for-hpa This adds the compiler prefix used in Debian/Ubuntu to the list (amd64-mingw32msvc-). Too bad /bin/sh doesn't support brace expansion. -- -Gene

Chen, 2011/5/13 陈晓宇 <xychen0921 at gmail.com>: > ../llvm2.9/configure --prefix=/home/AutoESL/llvm-obj >                             --host=x86_64-w64-mingw32 >                             --disable-multilib Please try with "--build=x86_64-w64-mingw32", not "--host". If you would still have any troubles, make sure your x86_64-w64-g++.exe can generate correct

Hi, I tried to do a build with CMake, Ninja, and MinGW32 and MinG64 respectively: MinGW32 failed on an missing sys/mman.h (POSIX-specific header): D:/test/llvm-trunk/projects/compiler-rt/lib/enable_execute_stack.c:13:22: fatal error: sys/mman.h: No such file or directory #include <sys/mman.h> ^ MinGW64 failed on an #error directive:

Hi, Trying to build llvm.dll (8.0.0) with mingw64 (gcc 8.1.0) using cmake. After linking for hours and consuming some 7GB of RAM, ld.exe finally bails out with: X:/tools/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: Error: export ordinal too large: 283482 The command I used is: cmake \ -DLLVM_TARGETS_TO_BUILD=X86 \ -DCMAKE_BUILD_TYPE=Debug \

I have successfully installed the cross compiled dll's and other files supplied by centos 7 on a machine running Windows 7. When I run GtkLauncher.exe it comes up with the google page displayed. However, when I try to view "http://www.msnbc.com" Gtklauncher crashes in libjavascriptcore.dll at offset 0xa4944. nfl.com comes up, but then crashes in the same place. My questions

Hello First of all, note the "llvm" in the mailing list title. Clang questions should be asked in other ML. > 3. Run cmake and let it figure out that its using Clang on Windows. > 4. Build and realize that the link doesn't work because CMake pulls in the > wrong libraries (per default it uses Microsoft naming conventions: foo.lib > instead of libfoo.a). It seems like

Just ran into the same problem, but with `-DLLVM_BUILD_TOOLS=ON` since the tools link against shlib and use the C++ interface I can't use Cosmin's solution. I managed to get through with using `RelWithDebInfo` instead of `Debug` On Sat, Jun 22, 2019 at 5:20 AM Cosmin Apreutesei via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Update: looks like the the problem was that the

Hi again, I am regularly building my small STL-enabled C++ project using Mingw64 on Windows x64 and the program runs fine (it builds and runs fine on x64 Linux too). Then I got brave and decided to try out Clang, because I'd eventually like to take a look at the quality of the generated code, and then did the following: 1. Set CC to clang. 2. Set CXX to clang++. 3. Run cmake and let it

Chen, see http://llvm.org/docs/GettingStarted.html#pf_12 ...Takumi ps. Excuse me, PE+ (aka pep) means "Executable file format for WIndows x64". 2011/5/16 陈晓宇 <xychen0921 at gmail.com>: > The stack trace: > > Starting program: > C:\MinGW\msys\1.0\home\xchen\llvm-obj\lib\Target\CellSPU/../.. > /../Debug/bin/tblgen.exe -I

hi ,everyone I have finished compiling of R 64 bit on 64 bit Windows system by using MINGW64, include the standard and recommended packages.tested it on Windows 2008 server R2 X64.it run very well.I wander anyone interested in it ,and anyone who want to continue testing  it with me?  and who can provide a space let me upload the R files Best wishes!                    2010/1/4                    

I was building llvm2.9 using MinGW64 on windows, msys was 32 bit so I specified --host option for a cross compiling. Following are my configure options: ../llvm2.9/configure --prefix=/home/AutoESL/llvm-obj --host=x86_64-w64-mingw32 --disable-multilib The error: make[1]: Entering directory `/home/AutoESL/llvm-obj/lib/VMCore' make[1]: ***

Dear mailing list: the attached diff implements a table-driven disassembler for the X86 architecture (16-, 32-, and 64-bit incarnations), integrated into the MC framework. The disassembler is table-driven, using a custom TableGen backend to generate hierarchical tables optimized for fast decode. The disassembler consumes MemoryObjects and produces arrays of MCInsts, adhering to the

Hi Sean, > the attached diff implements a table-driven disassembler for the X86 > architecture (16-, 32-, and 64-bit incarnations), integrated into > the MC framework. The disassembler is table-driven, using a custom > TableGen backend to generate hierarchical tables optimized for fast > decode. The disassembler consumes MemoryObjects and produces arrays > of

I just downloaded samba-1.9.18p8 and tried to compile it on Sun Solaris 2.5.1. I found out from the note in Makefile that I can not use the cc compiler coming from Solaris. It requires gcc, but I do not have gcc on my system. Spent about an hour on the Internet, but did not find suitable gcc for Sun Solaris. Can anyone who has compiled samba on Sun Solaris share your experience? Where can I

Hi, My New Year's resolution is to complain (constructively) whenever I get a spurious build failure email from a buildbot. For new or infrequent contributors especially, they can be extremely confusing and unnecessarily alarming. This one below is the first build ever attempted by the builder, so how on earth can it have come up with a meaningful blame list? And in any case, surely we

I'm getting this: /home/ghost/Work/llvm-cvs/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp: In member function `void llvm::SelectionDAGLowering::visitSetCC(llvm::User&, llvm::ISD::CondCode, llvm::ISD::CondCode, llvm::ISD::CondCode)': /home/ghost/Work/llvm-cvs/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:1107: error: ` UnsafeFPMath' undeclared (first use this function)

On Tue, Nov 01, 2011 at 10:34:43PM +0800, Jush Lu (?c?|?s) wrote: > Hi all, > > We are developing a linker, MCLinker. > > MCLinker is a linker for LLVM. It leverages the LLVM machine code (MC) > layer to link object files and bitcodes, and generate shared objects > and executable files. Cool! A linker has been the largest gap for FreeBSD to move to a completely BSD

Hi Folks, I am trying to get my wireless network card work under dom0 of XEN. I could successfully install the ndiswrapper drivers and could see it being associated to AP. However I amn''t able to transmit any packets outbound. I could''nt even ping the AP. Interestingly when I run a tcpdump I can see few broadcast packets on the interface. There no rules in iptables for nat or

Tracking down a problem with one of our benchmark codes, we've discovered that some of the patterns in X86InstrX86-64.td are wrong. Specifically: def MOV64toPQIrm : RPDI<0x6E, MRMSrcMem, (outs VR128:$dst), (ins i64mem:$src), "mov{d|q}\t{$src, $dst|$dst, $src}", [(set VR128:$dst, (v2i64 (scalar_to_vector