[MacPorts] #60091: i686-w64-mingw32-gcc-nothreads build failure - Segmentation fault

[MacPorts]

#60091: i686-w64-mingw32-gcc-nothreads build failure - Segmentation fault
-----------------------------------+----------------------
  Reporter:  mmaenz                |      Owner:  mojca
      Type:  defect                |     Status:  assigned
  Priority:  Normal                |  Milestone:
 Component:  ports                 |    Version:  2.6.2
Resolution:                        |   Keywords:  catalina
      Port:  i686-w64-mingw32-gcc  |
-----------------------------------+----------------------
Changes (by ryandesign):

 * cc: Gcenx, ryandesign (added)


Comment:

 Replying to [comment:10 Gcenx]:
 > I did a few changes to the Portfile that might not have been needed
 (I’ll edit the comment or comment again after work), I did blacklist
 XCode11 now building from source using macports clang-9 I got a completed
 build.
 >
 > The same blacklisting of XCode11 was applied to the X86_64 package and
 for good measure also onto the mingw-w64 meta package (not sure if it’s
 required or not)
 >
 > I pre-installed clang-9.0 since it failed to installed due to a missing
 package when called via mingw-w64

 Can you be more specific? What error message did you get exactly?

 > Edit;
 > I believe I’ve figured that out and will do a pull-request later that
 resolves the issue.

 I think you mean https://github.com/macports/macports-ports/pull/6449? But
 you closed it saying blacklisting wasn't what fixed it, it was just
 building everything from source that fixed it.

 > Just an FYI the mingw binutil conflict isn’t related and was caused by
 the xz version bump


 Replying to [comment:11 Gcenx]:
 > @mojca the issue here isn't with the Portfile here exactly but the
 prebuilt packages.
 >
 > Removed all ports, edited `macports.conf` and set `buildfromsource
 always` now `i686-w64-mingw32-gcc-nothreads` built without issue.

 Can you be more specific? Which packages need to be rebuilt? When Catalina
 was first released, we of course built all of our packages for it with
 Xcode 11. If there was some bug in Xcode 11 that caused a package to be
 mis-built in some way, and rebuilding that package with Xcode 11.4.1 would
 fix it, we can do that by revbumping the affected port, we just need to
 know which port(s) to do that to. If you have any information about what
 specifically is wrong with the affected packages that might be helpful as
 well for possibly identifying other affected packages.

-- 
Ticket URL: <https://trac.macports.org/ticket/60091#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS