similar to: [LLVMdev] llvm with gcc-4.8 / Intrinsics.gen.tmp Segmentation fault

Hi! I'm trying to crosscompile llvm/clang to run Windows. But the compilation fails: gmake[2]: Entering directory `/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/tools/lli' llvm[2]: Linking Release executable lli (without symbols) x86_64-w64-mingw32-g++ -I/usr/home/solskogen/mingw-w64-builder/bin/llvm/include -I/usr/home/solskogen/mingw-w64-builder/bin/llvm/tools/lli

On 10.11.2015 20.18, Gordon Messmer wrote: > On 11/10/2015 10:14 AM, Christer Solskogen wrote: >> Queued TRIM seems to be a problem with this kind of drive (with the >> latest firmware), and a "recent" kernel (4.1.x) seems to have this >> fixed this without disabling NCQ completely. Is that patch backported >> to the "mainline" CentOS 6 or CentOS7

Queued TRIM seems to be a problem with this kind of drive (with the latest firmware), and a "recent" kernel (4.1.x) seems to have this fixed this without disabling NCQ completely. Is that patch backported to the "mainline" CentOS 6 or CentOS7 kernel? -- chs

On 10.11.2015 22.00, Joseph L. Brunner wrote: > We have used that drive for 2 years with no issues. > > Amazing how much trouble people can get into when they tweak stuff... > Huh, like upgrading the firmware? -- chs

We have used that drive for 2 years with no issues. Amazing how much trouble people can get into when they tweak stuff... -Joe -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Christer Solskogen Sent: Tuesday, November 10, 2015 03:01 PM To: centos at centos.org Subject: Re: [CentOS] Samsung evo 840 fixes On 10.11.2015 20.18,

I need to build libLLVM (individual static libraries are fine at the moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and (separately) x86_64-w64-mingw32-gcc. I'd like this to work from both Linux and Cygwin build environments. With autotools, this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on

When trying to compile R on Windows 10 64-bit using LTO as I always do, I encountered a segmentation fault early in the compilation. I am uncertain as to what it means (please see below for error extract). I am using the most recent version of Rtools43 (5863) and updated its libraries prior to starting the build. My EOPTS is " -march=native -pipe -mno-rtm" and my

1 hour ago I downloaded llvm-3.6.0-rc4-win32.exe from http://llvm.org/pre-releases/3.6.0/ . I tried to compile simple C code that just print "hello" , but it didn't compile , because clang.exe can't find . when I use clang-cl.exe with the same code , it worked . I also have the same problem with clang++ even with , I add -I flag to GCC (4.9.1) C++ headers , the result:

hello everyone: On this boring weekend, I tried compile R-trunk on windows 11 arm64 using clangarm64+msys2 on macbook m1 , it surprisingly easy to compiled and run. more investigation and test and code modify need to be done ,but IMO this is a good beginning !! to compile R on windows 11 arm64 just need : 1 svn checkout R-trunk and add USE_LLVM=YES in MKRules.dist or Mkrules.local 2 install

Hi Ruben, Try adding a --build=x86_64-gnu-linux option to configure as well. I don't have that configuration locally, so I can't check to be certain, but IIRC, our configure wants all three for a cross compile like this. -Jim On Aug 21, 2011, at 7:19 AM, Ruben Van Boxem wrote: > Hi, > > I'm getting a returning build failure when building a linux->windows >

Hi, I'm getting a returning build failure when building a linux->windows crosscompiler out of LLVM/Clang. Attached is config.log and below is the output of "make VERBOSE=1" llvm[2]: Linking Release executable FileCheck (without symbols) g++ -I/home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/include

Hi, I have attached my compressed config file. Thanks, Reza > On Aug 20, 2019, at 12:03 PM, Daniel P. Berrangé <berrange@redhat.com> wrote: > > Re-adding the mailing list CC - please don't drop it. > > On Tue, Aug 20, 2019 at 11:54:34AM -0400, reza shahriari wrote: >> Hi, >> >> I am using msys2. When I run `./configure` without any parameters

I use Sony (previously Sonic Foundry) Sound Forge, which allows me to save audio files in .w64 (Wave 64) format to get around the 2GB .wav file limitation. W64 was invented by Sonic Foundry, and is an open format as far as I know. The only programs I know about using the .w64 format at the moment are Sound Forge and Steinberg Nuendo, although there may be others out there. With increasing

On Mon, Sep 14, 2015 at 8:49 PM, Jeroen Ooms <jeroen.ooms at stat.ucla.edu> wrote: > I tested this hypothesis by replacing '__GNUC__ <= 4' with '__GNUC__ > <= 5' and rebuilding R, but this introduces a whole lot of problems > that were not there before. In particular R crashes when using the > graphics device, which it did not without this fix. I found

When building LLVM/Clang, I get the following build failure: [ 4%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Signals.cpp.obj In file included from M:\Development\Source\LLVM\lib\Support\Signals.cpp:33: M:\Development\Source\LLVM\lib\Support/Windows/Signals.inc:48:17: error: redefinition of '_IMAGEHLP_LINE64' typedef struct _IMAGEHLP_LINE64 { ^

On 11/10/2015 10:14 AM, Christer Solskogen wrote: > Queued TRIM seems to be a problem with this kind of drive (with the > latest firmware), and a "recent" kernel (4.1.x) seems to have this > fixed this without disabling NCQ completely. Is that patch backported > to the "mainline" CentOS 6 or CentOS7 kernel? Can you provide any references to the specific bug

Yeah, I have about 50 of them in raid cards and doing software raid. Never done that. :) No need. We have yet to have one fail in 2 years :) -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Christer Solskogen Sent: Tuesday, November 10, 2015 06:17 PM To: centos at centos.org Subject: Re: [CentOS] Samsung evo 840 fixes On

Hi, [This is a follow-up to the "New version of Rtools for Windows" thread in January, but I just subscribed and don't know how to reply to an old thread -- my apologies.] I was able to use the nuwen distro to build a gcc 4.9.2 toolchain and use it to build the latest R-patched with it. Below are some notes about what I did; I hope they will be useful for keeping Rtools

Hi, I tried to compile R-2.10.0 src on 64 bit window. After install Rtools and wingw-w64 compiler and put it the first of my PATH variable, but i got the following error when i tried to compile. Anything I missed? thank you. x86_64-w64-mingw32-gcc -std=gnu99 -I../include -I. -I../extra -DHAVE_CONFIG_H -D R_DLL_BUILD -O3 -Wall -pedantic -DR_ARCH='"x64"' -c malloc.c -o

For future reference: https://sourceforge.net/p/mingw-w64/mailman/message/35747206/ On Wed, Mar 22, 2017 at 2:12 PM, Jeroen Ooms <jeroenooms at gmail.com> wrote: > This looks like a bug in mingw-w64 CRT. The problem can be produced > with C++ without R: > > #include <iostream> > #include <cmath> > #include <complex> > > int main(){ >