mingw-w64

Why is “MINGW64” appearing on my Git bash?

旧街凉风 提交于 2019-12-03 18:22:29
问题 I had to format my laptop, and so I had to install Git again. However it is quite different from the one I had yesterday, the icon is not the default orange one anymore, it looks more like Chrome now. The bash is quite different, including a purple " MINGW64 " in every line. Why is it there? Is this the new final version? Or did I download something different? I downloaded https://github.com/git-for-windows/git/releases/download/v2.5.1.windows.1/Git-2.5.1-64-bit.exe from https://git-scm.com

libtool: undefined symbols not allowed in i686-pc-mingw32 shared

邮差的信 提交于 2019-12-03 17:10:56
I'm using autotools as build system for a library of mine. Recently library is ported to Windows. Library compiles and links successfully though I encountered a strange error. There is only static libraries after configure and make. Evertything looks OK except a warning from libtool : libtool: undefined symbols not allowed in i686-pc-mingw32 shared I have exported all symbols for Windows machines by this code: #ifdef _WIN32 # ifdef DLL_EXPORT # define LIBRARY_API __declspec(dllexport) # else # define LIBRARY_API __declspec(dllimport) # endif #endif #ifndef _WIN32 # define LIBRARY_API #endif

MinGW GCC 4.9.1 and floating-point determinism

非 Y 不嫁゛ 提交于 2019-12-03 12:21:43
I wrote a small program to compute the Euclidean norm of a 3-coordinate vector. Here it is: #include <array> #include <cmath> #include <iostream> template<typename T, std::size_t N> auto norm(const std::array<T, N>& arr) -> T { T res{}; for (auto value: arr) { res += value * value; } return std::sqrt(res); } int main() { std::array<double, 3u> arr = { 4.0, -2.0, 6.0 }; std::cout << norm(arr) - norm(arr) << '\n'; } On my computer, it prints -1.12323e-016 . I know that floating point types should be handled with care. However, I thought that floating-point operations were at least somehow

Sorry, unimplemented: 64 bit mode not compiled in

不羁岁月 提交于 2019-12-03 05:56:41
This is what I'm trying to do(on Windows 7 64-bits): g++ -m64 -o main main.cpp And the error I get is: Sorry, unimplemented: 64 bit mode not compiled in ... I installed mingw-64-install.exe from here: https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/installer/ But I still get the same error. Do I also need to add the path to this folder in the environment variable? Thanks EDIT: This is what I get when I type g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/4.9.3/lto-wrapper.exe

Why can't Git Bash run my executable?

偶尔善良 提交于 2019-12-03 04:05:00
问题 I am on git-for-windows Git Bash. I can't run an executable on the command line: Pedr@Abc-07 MINGW64 /c/dev $ ls sqlite3.exe sqlite3.exe* Pedr@Abc-07 MINGW64 /c/dev $ sqlite3 bash: sqlite3: command not found Why is it so? 回答1: To run a program in the current directory in bash, you put ./ in front of it. So in your case: $ ./sqlite3.exe When you run sqlite3 , bash will look for a program with exactly that name in all directories of the PATH environment variable, which by default includes

The procedure entry point __gxx_personality_sj0 could not be located in…

我怕爱的太早我们不能终老 提交于 2019-12-03 01:50:36
I have managed to (somehow) cross-compile Qt5 with the Mingw-w64 Project's compiler for 32-bit Windows. All of the libraries have been installed to ~/i686-w64-mingw32 . I have a CMake-based Qt project that I am trying to cross-compile. By following these instructions , I have been able to get the project to compile. So far so good. Unfortunately, when executing the resulting binary on Windows, I end up getting an error: "The procedure entry point __gxx_personality_sj0 could not be located in the dynamic link library [application_name].exe" * [application_name] is the full path to the main

Python 3.4: compile cython module for 64-bit windows

萝らか妹 提交于 2019-12-03 00:14:52
I have a .pyx module that I've been trying to compile for use with 64-bit python 3.4 on Windows through various means but with no success. After a lot of trial and error, it does compile with python setup.py build_ext --inplace --compiler=mingw32 but of course, that won't work with 64-bit python. With msvc as the compiler, the error is File "C:\Python34\lib\distutils\msvc9compiler.py", line 287, in query_vcvarsall raise ValueError(str(list(result.keys()))) ValueError: ['path'] Windows 7 Microsoft Windows SDK for Windows 7 and .NET Framework 4 installed There appears to be some Microsoft Visual

Windows环境下的C/C++编译器

梦想的初衷 提交于 2019-12-02 18:54:46
编译器介绍 在Windows系统下的C/C++开发一般是以VS(Visual Studio)为主的,在Linux上则是GCC占据主导地位,这两种编译器是和其对应的操作系统紧密联系在一起的。伴随着计算机技术的发展,也出现了GCC的Windows移植版。虽然Microsoft的CL编译工具仍然只支持Windows,但其推出的 Visual Studio Code 作为一款跨平台的代码编辑器也收获了不少好评,可在GitHub上查看其 版本历史 。 查阅网上资料,目前Windows系统下的编译器大概有以下几种: Visual Studio , 微软自家开发,最新版VS 2017。一般商业公司会采用这种集成化的开发环境(IDE),配合丰富的插件扩展(如Visual Assist),开发调试起来非常方便,个人开发者可免费使用其社区版,也不失为一个不错的选择。 GCC ,GNU C/C++ Compiler,功能强大而开源, 推荐使用 。 其他编译器。在对运行性能有很高要求的领域,可能上述编译器并不合适,因此还有Intel的编译器,PGI编译器等,功能强大但支持平台有限。另外还有一些小众的编译器,当然其中不乏著名的Borland公司的Turbo C,Turbo C++等没落的王者。。。 Windows下的GCC 一般我们不会只使用gcc一个工具,而是希望使用和它相关的一套工具,例如g++,

Program with protocol-buffers don't compile with MinGW-w64: “undefined reference to google::protobuf:: …”

倖福魔咒の 提交于 2019-12-02 08:03:55
I have installed the libprotobuf-dev=2.6.0-4 and protobuf-compiler=2.6.0-4 packages from Debian Jessie repository. Now I'm trying to compile a program that use the 'addressbook.proto' file from the Google Developers example with the MinGW-w64 compiler. I'm using Ubuntu 14.04. With this command the program works: $ g++ main.cpp addressbook.pb.cc -lprotobuf But I want to compile for Windows too. I added the symlink: /usr/include/google -> /usr/i686-w64-mingw32/include/google . $ i686-w64-mingw32-g++ main.cpp addressbook.pb.cc -lprotobuf /usr/bin/i686-w64-mingw32-ld: cannot find -lprotobuf

Why is a static thread_local object in C++ constructed twice?

爷,独闯天下 提交于 2019-12-01 16:26:16
This code: #include <iostream> #include <thread> #include <mutex> struct Singl{ Singl(Singl const&) = delete; Singl(Singl&&) = delete; inline static thread_local bool alive = true; Singl(){ std::cout << "Singl() " << std::this_thread::get_id() << std::endl; } ~Singl(){ std::cout << "~Singl() " << std::this_thread::get_id() << std::endl; alive = false; } }; static auto& singl(){ static thread_local Singl i; return i; } struct URef{ ~URef(){ const bool alive = singl().alive; std::cout << alive << std::endl; } }; int main() { std::thread([](){ singl(); static thread_local URef u; }).join();