similar to: MinGW-w64 build of 64-bit R for Windows

This post updates https://stat.ethz.ch/pipermail/r-devel/2010-January/056301.html https://stat.ethz.ch/pipermail/r-devel/2010-January/056411.html The MinGW-w64 snapshots have moved back to gcc pre-4.4.4 (from pre-4.5.0) with static linking to C++ and Fortran run-time DLLs, and seem more stable. Currently the CRAN package check pages at http://cran.r-project.org/web/checks/check_summary.html

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, Has anyone built llvm-gcc-4.2-2.9 using mingw-w64 on Windows 7 64-bit OS? The binaries available in the download website LLVM-GCC 4.2 Front End Binaries for Mingw32/x86<http://llvm.org/releases/2.9/llvm-gcc4.2-2.9-x86-mingw32.tar.bz2> do not build applications (not surprisingly) for 64-bit Windows 7 (-m64 is disabled). I am both compiling and linking an application (to produce a

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

recently I used gcc 4.9.1 (http://sourceforge.net/projects/mingw-w64/files/Toolchains targetting Win64/Personal Builds/mingw-builds/)on windows to build R,but failed when link R.dll ,it report linker status 5.  after some digging, I found when use gcc 4.9.1 64 bit on windows there are lots of .refptr.*(* is r function name) in R.def, which lead build fail.so I add a simple path to

Hi, I've been hacking around something missing in the assemble for the mingw-w64 targets the tfloat variable. I did some research into the llvm sources and did see x86_fp80 which seems to be the same thing. Can we support the .tfloat variable or the alternative ? Or is it under another name? I've tried using .x86_fp80 instead but to no avail. :/ Here is how tfloat is being used in

We have been asked for a couple of years about builds of R for 64-bit Windows, e.g. at UserR 2006. Users of 64-bit Windows still seem very thin on the ground, but apparently 'Microsoft scraps 32-bit operating systems Microsoft has announced that Windows Server 2008 will be the last 32-bit system it releases, for servers or clients, as it makes its way fully into the world of

Hi people, I fixed the problem by renaming the function and every instance of 'rint' to 'rint_az' (Round Int Away from Zero) and then encoder_example.c built successfully. Don't know if this needs to be patched upstream or not. Edgar On 6/1/2017 2:53 PM, Edgar Reynaldo wrote: > Hello, > > I recently attempted to build theora 1.1.1 with mingw-w64-gcc 7.1 and

The CrossCompile module is in a perpetual state of "when I get a chance...", and desperately needs some cleanup. The problem you are hitting is caused by setting CMAKE_SYSTEM_NAME. When you set that CMake sets a variable CMAKE_CROSS_COMPILING. That variable should only be set when your host OS doesn't match your target OS. Since LLVM needs to build host-capable tools there is some

Hello, I recently attempted to build theora 1.1.1 with mingw-w64-gcc 7.1 and msys and it fails to build the encoder_example.c example program. There are multiple declarations of the function 'rint'. The source file created its own version of the function that rounds AWAY from zero. MinGW-W64 has its own version of the 'rint' function, which does not round away from zero.

Thank you for the feedback. This is cross-compiling for mingw-w64-x86_64 using gcc-5.3.0 and mingw-w64-4.0.4 on GNU/Linux. Upon attempting to compile now, a large number of errors occur in flac/decode.c which I have placed at the end of this email. They are eased by adding this to decode.c: #if _WIN32 #include <windows.h> #include <shlobj.h> #endif ...among the headers. Then, this

Hello, Upon compiling the flac tree today, after many successful compilations over the last few weeks, a new error is appearing before compilation bails out. This is a cross-compilation using gcc-5.3.0 running on GNU/Linux, with the objects being built for a mingw-w64-x86_64 host. Among other things, the compiler is looking for windows_unicode_filenames.h but it isn't there. Also, I'm

The following tiny patches make opus and opusfile to use xmm intrinsics for lrintf() with mingw-w64 builds when targetting x64 instead of their default x87 asm. Regards. -- O.S. diff --git a/celt/float_cast.h b/celt/float_cast.h index ed5a39b..b9b8484 100644 --- a/celt/float_cast.h +++ b/celt/float_cast.h @@ -61,7 +61,14 @@ ** the config.h file. */ -#if (HAVE_LRINTF) +#if

On 2012-12-28 2:49 AM, Erik de Castro Lopo wrote: > J. Hendricks wrote: > >> This is a patch to allow building of the project using MSYS, MinGW, and >> MinGW-w64 with the following invocation: > Hi, > > Sorry, your patch doesn't apply. Its probably a problem with line > wrapping. > > Can you please re-send a gzipped version of it? > > Cheers, > Erik

You may be the first person to try this configuration... it would certainly be good if libffi could be made to work and these tests passing, try to see what the problem and patch it. 2015-07-28 22:04 GMT+03:00 Martell Malone <martellmalone at gmail.com>: > Is it turned ON in your build? >> > Yes it is turned on in my build > > here is my build script > >

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

> > Is it turned ON in your build? > Yes it is turned on in my build here is my build script PATH=/mingw64/bin:$PATH FFI_INCLUDE_DIR="$(pkg-config --cflags libffi)" > FFI_INCLUDE_DIR=$(echo $FFI_INCLUDE_DIR | sed 's|-I||g') > > /mingw64/bin/cmake.exe \ > -G"MSYS Makefiles" \ > -DCMAKE_MAKE_PROGRAM="/usr/bin/make.exe" \ >

I realize that it isn't much of an improvement, but AIFF supports 4GB recordings, and flac is compatible with this. Being an avid "taper" myself, I have, on many occasions recorded up to this limit, and I always back up my original recordings using flac. W64 support is more than welcome, but AIFF support gets you twice the length right away. Brian Willoughby Sound

Our DAW REAPER (www.reaper.fm) supports W64 as well. We'd be happy to share our W64 reading/writing implementations if someone wishes to integrate them into flac... -Justin Chris Cantwell wrote: > > 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

On Tue, Jul 28, 2015 at 10:12 PM, Yaron Keren <yaron.keren at gmail.com> wrote: > You may be the first person to try this configuration... it would certainly > be good if libffi could be made to work and these tests passing, try to see > what the problem and patch it. I hit a similar problem on Linux but only with gcc5 as host compiler, see