mingw-w64

Stack test output garbled on MINGW64

柔情痞子 提交于 2019-12-13 00:33:00
问题 I'm running GHC using Stack on Windows 10, and using Git Bash (MINGW64) for much of my daily workflow. That includes using GHC and GHCi, which generally works fine. However, when I run stack test from MINGW64, the output is garbled by ANSI color codes: $ stack test UC-0.1.0.0: test (suite: UC-test) [?25lSorting Group 1: [2K[1F prop1: [[92mOK, passed 100 tests[0m] [2K[1F prop2: [[92mOK, passed 100 tests[0m] Properties Total Passed [92m2[0m [92m2[0m Failed 0 0 Total [92m2[0m [92m2[0m [?25h

#error Only Win32 target is supported

泄露秘密 提交于 2019-12-12 19:11:22
问题 I am using cygwin64 and including the MinGW64/x86_64-w64-mingw32/include folder in my project. However I am getting the following error when I run make on the project : /cygdrive/c/MinGW64/x86_64-w64-mingw32/include/sys/types.h:10:2: error: #error Only Win32 target is supported! I would think that that since the types.h file appears to be in a 64 bit folder it would support the 64 bit system, so what am I misunderstanding in this system. The code in types.h that it gets caught on is as

Why does MinGW-w64 require winsock2 to be manually included?

孤街醉人 提交于 2019-12-12 16:12:59
问题 Some code and associated warnings/errors: #include <windows.h> #include <iphlpapi.h> int main() { } F:/Prog/mingw-w64/x86_64-4.9.2-win32-seh-rt_v3-rev1/mingw64/x86_64-w64-mingw32/include/ws2ipdef.h:71:3: error: ' ADDRESS_FAMILY ' does not name a type ADDRESS_FAMILY si_family; #include <windows.h> #include <winsock2.h> #include <iphlpapi.h> int main() { } // this compiles successfully, only gives warning F:/Prog/mingw-w64/x86_64-4.9.2-win32-seh-rt_v3-rev1/mingw64/x86_64-w64-mingw32/include

std::thread, posix threads, and win32 threads in MinGW-W64

天涯浪子 提交于 2019-12-12 09:06:10
问题 I'm using MinGW_W64, and I'm having trouble deciding how to move forward with the "threading" option. I can use either posix threads, or win32 threads. So far I've been using C++11's "std::thread" for my threading (which requires the posix threads option), and I really like the interface doing things this way. However, I've read from multiple sources that posix threads are significantly slower than win32 threads, and performance is a big concern for me. My project will eventually be multi

Compile freetype-2.4.9 with MinGW-w64/Cygwin

ぐ巨炮叔叔 提交于 2019-12-12 05:17:40
问题 I'm trying to build x86_64 (64-bit code) version of the freetype-2.4.9 with native MinGW-w64 compiler in Cygwin environment. The configure runs fine but the makefile fails. Jarmo@UltraJATmachine /cygdrive/y/tools/cppkirjastot $ cd freetype-2.4.9/ Jarmo@UltraJATmachine /cygdrive/y/tools/cppkirjastot $ PATH=/cygdrive/y/Tools/Compilers/mingw64/bin:$PATH Jarmo@UltraJATmachine /cygdrive/y/tools/cppkirjastot/freetype-2.4.9 $ ./configure --build=i686-pc-mingw32 --disable-shared FreeType build system

Undefined reference to curl_easy_init

▼魔方 西西 提交于 2019-12-12 02:38:21
问题 System Windows 7 64bit, Eclipse Mars + CDT, MinGW 64, curl source https://curl.haxx.se/download.html for Win64 - MinGW64 SSH SSL, have tried other versions with very same linker errors Code: #include <curl/curl.h> int main(void) { CURL * curl; curl = curl_easy_init(); if (curl) { curl_easy_cleanup(curl); } return 0; } The problem with linker errors: Info: Internal Builder is used for build g++ -DCURL_STATICLIB "-IC:\\Source\\curl-7.40.0-devel-mingw64\\include" "-IC:\\Source\\curl-7.40.0-devel

Possible to change distutils default compiler options?

北战南征 提交于 2019-12-11 17:42:37
问题 Win 10, x64, minGW64, Python 2.7, Anaconda I am trying to compile zbar for use in Python 2.7 using python setup.py build --compiler=mingw32 Here's setup.py from distutils.core import setup, Extension from distutils.sysconfig import get_config_vars setup( name = 'zbar', version = '0.10', author = 'Jeff Brown', author_email = 'spadix@users.sourceforge.net', url = 'http://zbar.sourceforge.net', description = 'read barcodes from images or video', license = 'LGPL', long_description = open('README'

Export COMMON block from DLL with gfortran

旧巷老猫 提交于 2019-12-11 11:34:13
问题 I am having trouble correctly accessing a variable in a Fortran DLL from a Fortran EXE when the variable is part of a COMMON block. I have a trivial code simple.f90 which I compile into a DLL using MSYS64/MinGW-w64 gfortran 9.2 as x86_64-w64-mingw32-gfortran simple.f90 -o simple.dll -shared ! simple.f90 module m implicit none integer :: a, b !common /numbers/ a, b end module subroutine init_vals use m implicit none a = 1 b = 2 end subroutine This library is used from a even simpler program

Unable to run windows binary compiled with clang/lld/mingw

人盡茶涼 提交于 2019-12-11 11:27:03
问题 I have downloaded and installed clang on windows 10 from http://releases.llvm.org/download.html and mingw from https://sourceforge.net/projects/mingw-w64/ I am trying to compile a very basic C program using clang/lld/mingw: int main(int argc, char* argv[argc + 1]) { return 0; } To compile I invoke: clang.exe -target x86_64-windows-gnu -fuse-ld=lld.exe -g -gcodeview -Wl,/debug,/pdb:example.pdb example.c -o example.exe This creates an exe which faults on startup in mainCRTStartup (__security

Compile C++ as 64Bit with CLion

杀马特。学长 韩版系。学妹 提交于 2019-12-11 10:29:27
问题 I have a c++ application that runs a memory-consuming algorithm. It crushes with error : terminate called after throwing an instance of 'std::bad_alloc' after the allocated memory reaches about 2GB. I want to compile it as 64Bit so it could allocate more memory from my 64Bit/8GB Ram machine. How it can be done? Im working with CLion, building with CMake and using mingw version: mingw-w64\i686-4.8.3-posix-dwarf-rt_v3-rev2 btw - the wingw is installed under C:\Program Files (x86)\mingw-w64 is