search for: mingw32

...o" , 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: >C:\Users\One\Desktop>clang++ -I c:\MinGW\x86_64-w64-mingw32\include\c++ >main.cpp -lib=libstdc++ >In file included from main.cpp:1: >c:\MinGW\x86_64-w64-mingw32\include\c++\iostream:38:10: fatal >error:'bits/c++config.h' file not found >#include <bits/c++config.h> >1 error generated. I found bits/c++config.h in MinGW folde...

...n __mingw_CRTStartup () at ../mingw/crt1.c:244 #4 0x00401284 in mainCRTStartup () at ../mingw/crt1.c:264 Any idea what is going on here? I'm cross-posting to llvm-dev since I'm not sure if this is a Clang or LLVM codegen issue. Clang verbose output: clang version 3.2 Target: i686-pc-mingw32 Thread model: posix "C:/Users/jholewinski/projects/llvm/build/clang-x86-mingw32/bin/clang++.exe" -cc1 -triple i686-pc-mingw32 -S -disable-free -main-file-name test1.cpp -mrelocation-model static -mdisable-fp-elim -fmath-errno -mconstructor-aliases -target-cpu pentium4 -momit-leaf-frame-p...

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 -I/usr/home/solskogen/obj/_build/llvm.native.x86_64-w64-mingw32/include -I/usr/home...

Here is a curious observation. In > version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major 2 minor 0.0 year 2004 month 10 day 04 language R > Try the following: > Plot(c(1:100), type = "l + ") Warning message: plot type 'l ' truncated to first character in: plot.xy(xy...

...e --prefix=/usr -- >> enable-optimized --disa >> ble-shared --disable-multilib --disable-asserts >> Ok...I would have expected that to suppress the following error: >> output: >> llvm[1]: Compiling BasicBlock.cpp for Release build >> c:\mingw\bin\../lib/gcc/mingw32/4.3.0/include/c++/bits/ >> boost_concept_check.h: In >> member function 'bool __gnu_cxx::_EqualOpConcept<_First, >> _Second>::__constraint >> s_() [with _First = llvm::BasicBlock, _Second = llvm::BasicBlock*]': >> c:\mingw\bin\../lib/gcc/mingw32/4.3.0/...

...\ intl.o prefix.o version.o driver-i386.o ../libcpp/libcpp.a ../libib erty/libiberty.a ../libdecnumber/libdecnumber.a -L/c/Temp/msys-llvm/Release/lib -lpthread -lpsapi -limagehlp -lm /c/Temp/msys-gcc-build/./gcc/xgcc -B/c/Temp/msys-gcc-build/./gcc/ -L/c/Temp/msys -gcc-build/i686-pc-mingw32/winsup/mingw -L/c/Temp/msys-gcc-build/i686-pc-mingw32 /winsup/w32api/lib -isystem /c/Temp/llvm-gcc4.2-2.6.source/winsup/mingw/include -isystem /c/Temp/llvm-gcc4.2-2.6.source/winsup/w32api/include -B/c/Temp/msys-llv m-gcc/i686-pc-mingw32/bin/ -B/c/Temp/msys-llvm-gcc/i686-pc-mingw32/lib/ -isystem...

I would like to compile for Windows a rather simple R package that contains some C code. It does not contain any Fortran code. I tried the cross-compilation route using the pre-built set of tools from http://www.devolution.com/~slouken/SDL/Xmingw32/, as described in $R_SRC/src/gnuwin32/INSTALL Using the sources in r-devel from the rsync site I am able to build libR.a in src/gnuwin32 but I can't build the package. Using the sources in r-release-patched from the rsync site I am unable to build libR.a. The tail end of that compilation log...

...that particular issue, I was hoping it was something easy to fix on the compiler, since it compiles fine on Leopard. When assertions are disabled I get this error: llvm[1]: Compiling IntrinsicInst.cpp for Release-Asserts build In file included from IntrinsicInst.cpp:32: c:\mingw\bin\../lib/gcc/mingw32/4.3.0/include/c++/bits/ boost_concept_check.h: In instantiation of '__gnu_cxx::_SGIAssignableConcept<llvm::MachineMove>': c:\mingw\bin\../lib/gcc/mingw32/4.3.0/include/c++/bits/stl_vector.h: 179: insta ntiated from 'std::vector<llvm::MachineMove, std::allocator<llv...

Hi I tried to cross compile R under Linux but get an error. i586-mingw32-gcc -isystem /home/schouwl/unpack/mingw/include -O2 -Wall -pedantic -I../include -I. -DHAVE_CONFIG_H -DR_DLL_BUILD -c dynload.c -o dynload.o dynload.c: In function `R_loadLibrary': dynload.c:94: warning: implicit declaration of function `_controlfp' dynload.c:94: error: `_MCW_IC' undec...

...ative), for the mingw platform, I get this error: 'error: there are no arguments to `lrand48' that depend on a template parameter, so a declaration of `lrand48' must be available'. ------------------------ make[3]: Entering directory `/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw32/libstdc++-v3/testsuite' `/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw32/libstdc++-v3/scripts/testsuite_flags --build-cxx` -DHAVE_CONFIG_H -I. -I../../../../../../src/llvm-gcc-1/llvm-gcc/libstdc++-v3/testsuite -I.. -I/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw32/libstdc++-v3/inc...

...? Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C: \wetland_test>rcmd SHLIB -o wetall2.dll wetall.f90 gfortran -shared -s -static-libgcc -o wetall2.dll tmp.def wetall.o -LC:/PROGRA~1/R/R-212~1.1/bin/i386 -lR c:/rtools/mingw/bin/../lib/gcc/mingw32/4.5.0/libgfortran.a(unix.o):(.text$sprintf+0x1b): undefined reference to `__mingw_vsprintf' c:/rtools/mingw/bin/../lib/gcc/mingw32/4.5.0/libgfortran.a(main.o):(.text$sprintf+0x1b): undefined reference to `__mingw_vsprintf' c:/rtools/mingw/bin/../lib/gcc/mingw32/4.5.0/libgfortran.a(format.o)...

...ies\win32-open3\ext>ruby extconf.rb checking for ruby/io.h... no checking for rb_pid_t in ruby.h... yes creating Makefile C:\Documents and Settings\djberge\Repositories\win32-open3\ext>make make: *** No rule to make target `ruby.h'', needed by `open3.o''. Stop. I also tried mingw32-make with the same result: You can get the source here: git://github.com/djberg96/win32-open3.git Here''s some environment info: RubyGems Environment: - RUBYGEMS VERSION: 1.3.5 - RUBY VERSION: 1.8.6 (2009-08-04 patchlevel 383) [i386-mingw32] - INSTALLATION DIRECTORY: C:/Ruby/lib/r...

...I'm trying to solve is how get my cfrontend build configured properly. The usual symptom of an incorrect configuration is the inability to find various header files. Here's some example spew: $ /home/llvm_home/llvm-gcc-build/gcc/xgcc -v -B/home/llvm_home/llvm-gcc-build/gcc/ -Bc:/msys/1.0/mingw32/bin/ -Bc:/msys/1.0/mingw32/lib/ -isystem c:/msys/1.0/mingw32/include -isystem c:/msys/1.0/mingw32/sys-include -O2 -I../../llvm-gcc/gcc/../winsup/w32api/include -DIN_GCC -DCROSS_COMPILE -DDEFAULT_TARGET_MACHINE=\"mingw32\" -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes...

I posted this to the comp.lang.tcl newsgroup, but it might relate to a possible bug in the Mingw32 cross-build environment under CentOS 6 (or EPEL). Forwarded Message: From: Robert Heller <heller at deepsoft.com> Subject: Cross Building Tcl using Mingw32-gcc (4.9.2) Newsgroups: comp.lang.tcl Message-ID: <Nc-dnd1wRNTsy6PInZ2dnUU7-b-dnZ2d at giganews.com> Date: Mon, 27 Apr 2015 10:32...

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 Ubuntu, Cygwin, etc). I'...

#!/bin/bash #./configure-fedora-compile-mingw32.sh #./configure --host=i686-pc-mingw32 --with-lzo=./lzo-2.03/ --with-lzo-include=./lzo-2.03/include/ --with-lzo-lib=./lzo-2.03/ #./configure --host=i686-pc-mingw32 --with-lzo=./lzo/ --with-lzo-include=./lzo/include/lzo/ --with-lzo-lib=./lzo/ #./configure --host=i686-pc-mingw32 \ # --with...

...b*x+c*I(x^2),start=c(a=1,b=1,c=0.1),algorithm="port") confint(n1) ## boom N.B.: It only crashes if algorithm="port" is specified. ## [1] "Windows 2000 Professional (build 2195) Service Pack 4.0" ## ## > R.version ## _ ## platform i386-pc-mingw32 ## arch i386 ## os mingw32 ## system i386, mingw32 ## status ## major 2 ## minor 2.0 ## year 2005 ## month 10 ## day 06 ## svn rev 35749 ## language R...

...recap of the problem is that when cross-compiling LLVM itself the configure/make scripts get confused when creating the needed build host tools. For example, building and configuring like: CC_FOR_BUILD='i686-pc-linux-gnu-gcc' CXX_FOR_BUILD='i686-pc-linux-gnu-g++' CXX='i686-mingw32-g++' CC='i686-mingw32-gcc' LD='i686-mingw32-ld' /scratch /meadori/llvm-trunk/src/trunk/configure --host=i686-mingw32 CC_FOR_BUILD='i686-pc-linux-gnu-gcc' CXX_FOR_BUILD='i686-pc-linux-gnu-g++' CXX='i686-mingw32-g++' CC='i686-mingw32-gcc' LD=...

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 malloc.o x86_64-w64-mingw32-windres -I../include -i dllversion.rc -o dllversion.o x86_64-w64-mingw32-gcc -std=gnu99 -shared -s -mwindows -o R.dll R.def...

...that the GCC snapshot we are using isn't happy with mingw. In any case, I think it would be better to ask on the mingw lists to get some idea of what to do about this. -Chris > ------------------------ > make[3]: Entering directory > `/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw32/libstdc++-v3/testsuite' > `/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw32/libstdc++-v3/scripts/testsuite_flags > --build-cxx` -DHAVE_CONFIG_H -I. > -I../../../../../../src/llvm-gcc-1/llvm-gcc/libstdc++-v3/testsuite -I.. > -I/C/projects/build/MinGW/llvm-gcc-1-1/i686-pc-mingw...