similar to: [LLVMdev] llvm-gcc mingw-w64 64-bit version

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

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

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.

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

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

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

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 >

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

> > 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" \ >

A few days ago Gong Yu alerted this list to the possibility of building a 64-bit R for Windows under a recent MinGW-w64 toolchain, something we had failed to make work in 2007, 2008 and Feb 2009. We've now completed the port in the R-devel (SVN trunk) sources and are able to successfully complete 'make check-all'. An experimental installer based on this version is available at

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 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

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

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

Hi Josh, On Sat, 2004-10-09 at 22:41, Josh Coalson wrote: > --- Marek Peteraj <marpet@naex.sk> wrote: > > Hi all, > > > > i'd like to ask what the best options are for safe 24bit 96kHz > > archiving. Currently i'm only using -8 but there are also some other > > options like block size etc. Can anyone suggest? > > I haven't heard of

On Thu, Oct 6, 2011 at 2:00 PM, Ruben Van Boxem <vanboxem.ruben at gmail.com> wrote: > When building LLVM/Clang, I get the following build failure: > > MinGW-w64 provides the necessary typedefs and declarations. I adjusted the > ifdef's to include a check for a the MinGW-w64-specific symbol of choice to > differentiate mingw.org vs mingw-w64. Tested on i686-w64-mingw32 and

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 { ^

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 > >