Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42847 - [mingw-w64-gcc-base] package should not exist in the repos
Attached to Project:
Community Packages
Opened by Dave Reisner (falconindy) - Wednesday, 19 November 2014, 15:33 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 19 November 2014, 16:05 GMT
Opened by Dave Reisner (falconindy) - Wednesday, 19 November 2014, 15:33 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 19 November 2014, 16:05 GMT
|
DetailsIt seems to me that no one would ever need this package, as it's only useful for building "mingw-w64-gcc".
Can we get rid of this? |
This task depends upon
so we build -base package, then core lib stuff and then complete gcc with C++ support, etc.
Yes, gcc requires gcc, it is a known process called bootstrapping. But once you've built the binary you don't need stage1/2 anymore. See arm-none-eabi and avr- toolchains as another examples.
> until someone wants to build mingw
I assume these users know how to bootstrap toolchains. At least they had to do it for gcc.