Package Details: mingw-w64-gcc 9.3.0-1

Git Clone URL: (read-only, click to copy)
Package Base: mingw-w64-gcc
Description: Cross GCC for the MinGW-w64 cross-compiler
Upstream URL:
Licenses: GPL, custom, LGPL, FDL
Groups: mingw-w64, mingw-w64-toolchain
Provides: mingw-w64-gcc-base
Submitter: Barthalion
Maintainer: xantares
Last Packager: xantares
Votes: 54
Popularity: 1.74
First Submitted: 2018-01-07 17:33
Last Updated: 2020-03-13 20:37

Required by (190)

Sources (3)

Pinned Comments

xantares commented on 2018-03-07 17:54

To install this package from source I recommend to use:

aurman -S --noedit --solution_way --pgp_fetch mingw-w64-gcc

For a binary install I recommend to use Martchus ownstuff repo:

Latest Comments

1 2 3 4 5 6 ... Next › Last »

enanone commented on 2020-04-04 09:43

@Martchus It was exactly that! It was all my fault, I had installed mingw-w64-gcc-base but not this very package mingw-w64-gcc. I am still amazed that you could still figure it out without any further information O_o Thanks!

Martchus commented on 2020-04-03 15:23

You might end up having only mingw-w64-gcc-base installed (instead of mingw-w64-gcc). Not sure what the base package contains but maybe the C++ compiler is in fact missing there.

enanone commented on 2020-04-03 15:20

$ pacman -Qo /usr/bin/x86_64-w64-mingw32-g++
error: No package owns /usr/bin/x86_64-w64-mingw32-g++
$ ls /usr/bin/x86_64-w64-mingw32-g++
ls: cannot access '/usr/bin/x86_64-w64-mingw32-g++': No such file or directory

I am going to try to reinstall the package yet again, but I got no error the last time I did install it. Could you think of some common pitfalls that people might do during installation but throw no error?

Martchus commented on 2020-04-03 15:15

But you should have, e.g.

[root@martchus /]# pacman -Qo /usr/bin/x86_64-w64-mingw32-g++
/usr/bin/x86_64-w64-mingw32-g++ is owned by mingw-w64-gcc 9.3.0-1

If that's not the case something went wrong in the installation process of the package. I belief that the implementation of the pure C compiler even relies on C++ these days so you couldn't even configure the GCC build to disable g++.

enanone commented on 2020-04-03 14:56

@Martchus thank you for the quick answer! When running:

x86_64-w64-mingw32-gcc -Wall -O3 hello_world.cpp

I get

x86_64-w64-mingw32-gcc: error: hello_world.cpp: C++ compiler not installed on this system

Though this package installs x86_64-w64-mingw32-gcc, I do not have x86_64-w64-mingw32-g++

Martchus commented on 2020-04-03 12:55

@enanone This package contains g++ and libstdc++ (targeting Windows/mingw-w64 for i686 and x86_64) so you can use it to build C++ projects. That is consistent with the regular gcc package.

enanone commented on 2020-04-03 12:39

Is there anything comparable to this package but for C++?

Martchus commented on 2020-02-10 18:41

@xantares I suppose I'll be busy when GCC 10 comes out. At least too busy to rebuild all mingw-w64 package to use DW2 exception handling and fix possible build errors. So I guess I'll be using SJLJ a little bit longer in my binary repository and do the rebuild probably in June. I see no problem if you already enable DW2 when updating the AUR package to GCC 10. Just be aware that I'll need a little bit longer to adapt. But then I can finally add rust to update librsvg.

Because I've read about adding an interactive option in the previous comments: It is generally possible to use an environment variable for making things configurable. One can then define this variable in makepkg.conf to override the default. It might also make sense to simply provide an alternative PKGBUILD, e.g. mingw-w64-gcc-win32.

lberrymage commented on 2019-10-17 00:39

Thank you, that does make sense. I just didn't see anything in the wiki page on package guidelines.

Edit: I take that last sentence back. For anyone who stumbles across this and wishes to know where this is stated officially:

Morganamilo commented on 2019-10-17 00:35

PKGBUILDS should never be interactive