Package Details: mingw-w64-gcc 8.2.0-3

Git Clone URL: (read-only)
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: 32
Popularity: 1.831597
First Submitted: 2018-01-07 17:33
Last Updated: 2019-01-22 19:10

Required by (184)

Sources (5)

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 »

Martchus commented on 2018-12-26 11:49

I'm also thinking about dropping i686. But I haven't come to a conclusion yet. Somehow it seems wrong to remove that possibility even though it becomes less and less relevant in practise. Sometimes I still use the 32-bit version, at least for some packages.

I was also thinking about untying the architectures at least. Either do it like the Android packages in my PKGBUILDs repo or simply apply a few sed/awk commands in my build script before invoking makechrootpkg. The good thing about the last version would be that no packages had to be changed.

xantares commented on 2018-12-26 10:50

Maybe I'll switch to dw2 when gcc 9 gets out then.

You still use 32 bits binaries guys ?

Martchus I also use your repository often, thank you for maintaining it :)

Martchus commented on 2018-12-25 23:39

@Hagar Btw, there's also a GitHub issue about the DW2 topic:
If you gain some experience (especially regarding Qt applications), let me know.

Martchus commented on 2018-12-25 23:32


Beside Rust only supporting DW2, switching to that exception handling is likely the right thing to do anyways. I'm just waiting to update the ownstuff repository because I'm not 100 % sure about possible downsides and also it would mean recompiling over 200 packages.

The ownstuff repo is only hosted via my private VDSL. Still I'm wondering that you can't "quite often" access it because I don't have that often connection issues. I don't know how many people actually use the repository. If the number is high enough I (or someone) could create a mirror somewhere.

Hagar commented on 2018-12-25 23:10

To build rust the rust developers actually require that gcc be built using --disable-sjlj-exceptions rather than --disable-dw2-exceptions

I changed my gcc build and then had no problems building rust.

I then had to rebuild every mingw package to reflect this change.

I only build using makechrootpkg.

I have found the ownstuff repository to be flaky, quite often I cant access it.

pingplug commented on 2018-12-03 13:29

please add this patch to fix a gcc bug that breaks mingw-w64-rust build:

Martchus commented on 2018-11-15 18:58

@rubenvb This might still require patching for Windows (see

rubenvb commented on 2018-11-15 18:44

Can someone add the "--enable-libstdcxx-filesystem-ts=yes" flag to configure?

lukemontalvo commented on 2018-11-01 18:54

@CodingKoopa I was having the same issue, it seems to be that this package depends on mingw-w64-winpthreads which depends on mingw-w64-gcc-base but this package isn't being detected as providing it for some reason? Then mingw-w64-gcc-base depends on mingw-w64-headers-bootstrap which conflicts with mingw-w64-winpthreads.

I worked around it by installing mingw-w64-gcc-base and its dependencies first, then attempted to install mingw-w64-gcc. When pikaur failed but before it exited, I uninstalled mingw-w64-gcc-base and proceeded. A bit of a messy workaround but it worked!

luntik2012 commented on 2018-08-15 09:41


gpg --recv-key 93BDB53CD4EBC740