[Bug bootstrap/93758] Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault"

2021-07-18 Thread mojca at macports dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93758 --- Comment #4 from Mojca Miklavec --- I'm sorry, I forgot about this ticket. I can confirm that building (version 11.1) in fact works on all macOS versions at the moment https://ports.macports.org/port/x86_64-w64-mingw32-gcc/details/ It's

[Bug bootstrap/93758] New: Building x86_64-w64-mingw32-gcc (mingw-w64) on macOS Catalina results in "internal compiler error: Segmentation fault"

2020-02-15 Thread mojca at macports dot org
oduct: gcc Version: 9.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: mojca at macports dot org Target Milestone: --- See: * https://trac.macports.org/ticket/600

[Bug bootstrap/78756] Missing prefix in the name of gfortran.info

2020-02-15 Thread mojca at macports dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756 Mojca Miklavec changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug bootstrap/80865] New: broken compilation on Mac OS X 10.5 / powerpc: unrecognizable insn

2017-05-23 Thread mojca at macports dot org
Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: mojca at macports dot org Target Milestone: --- Created attachment 41409 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41409=edit Full build log from a broken gcc bu

[Bug bootstrap/78756] Missing prefix in the name of gfortran.info

2016-12-13 Thread mojca at macports dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756 --- Comment #3 from Mojca Miklavec --- And just for the reference, here's the commit that fixed the behaviour for us: https://github.com/macports/macports-ports/commit/0b41554b5c627dcd5d095b1b432f554993df4c90

[Bug bootstrap/78756] Missing prefix in the name of gfortran.info

2016-12-13 Thread mojca at macports dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756 --- Comment #2 from Mojca Miklavec --- I just wanted to confirm that doing the same kind of replacement for gfortran as our package manager does for gcc, I get the expected result. So gfortran's info file doesn't seem to behave any different

[Bug bootstrap/78756] Missing prefix in the name of gfortran.info

2016-12-13 Thread mojca at macports dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756 --- Comment #1 from Mojca Miklavec --- In the meantime I realized that the part of our build system that supports compiling cross-tools does the following: ---> Extracting gcc-6.2.0.tar.bz2 ---> Patching cpp.texi: s|setfilename

[Bug bootstrap/26500] [4.2 Regression] info/gfortran.info is no longer being installed

2016-12-09 Thread mojca at macports dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26500 Mojca Miklavec changed: What|Removed |Added CC||mojca at macports dot org --- Comment

[Bug bootstrap/78756] New: Missing prefix in the name of gfortran.info

2016-12-09 Thread mojca at macports dot org
: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: mojca at macports dot org Target Milestone: --- I'm trying to build GCC for the MinGW-w64 cross-compiler with fortran support. I end up with the following set of files: $prefix/share/info/gfortran.info $prefix/share