Opened 5 years ago

Closed 4 years ago

#59427 closed defect (fixed)

mono 6.0.0.319_0 Building Error on 10.15

Reported by: fuzunspm (Hüseyin Fahri Uzun) Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: catalina Cc: cjones051073 (Chris Jones)
Port: mono

Description

After upgrading my macOS to Catalina 10.15, mono can't be built with the error output below

Error: Failed to build mono: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mono/mono/main.log for details.
:info:build Exit code: 2
:error:build Failed to build mono: command execution failed
:debug:build Error code: CHILDSTATUS 70005 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_mono/mono/main.log for details.

Attachments (1)

main.log (303.9 KB) - added by fuzunspm (Hüseyin Fahri Uzun) 5 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 5 years ago by fuzunspm (Hüseyin Fahri Uzun)

Port: mono added

comment:2 Changed 5 years ago by ryandesign (Ryan Carsten Schmidt)

Please attach the main.log file so that we can see what went wrong.

Changed 5 years ago by fuzunspm (Hüseyin Fahri Uzun)

Attachment: main.log added

comment:3 Changed 5 years ago by fuzunspm (Hüseyin Fahri Uzun)

yes i forgot that sorry

comment:4 Changed 5 years ago by cjones051073 (Chris Jones)

info:build /bin/sh: line 1: 70602 Segmentation fault: 11 

means almost certainly another instance of the Xcode 11 'stack-check' issue.

comment:5 Changed 5 years ago by fuzunspm (Hüseyin Fahri Uzun)

So will i fix it or i should wait for it? I'm Asking because quick internet search about the issue did not provide any useful information

comment:6 Changed 5 years ago by cjones051073 (Chris Jones)

Someone (maintainer?) will need to investigate the appropriate fix for the port and to deploy it. If you are lucky, it might be enough to blacklist the Xcode 11 clang compiler (and thus fallback to MacPorts clang 9.0) but this is not always enough.

comment:7 Changed 5 years ago by cjones051073 (Chris Jones)

Cc: cjones051073 added

comment:8 Changed 5 years ago by cjones051073 (Chris Jones)

fuzunspm - Please take a look at the fix applied to redis in

https://github.com/macports/macports-ports/commit/e35f356df49a71148c38f8531b08b8a4abee926b#diff-c863911924e8a4d3140f5648ae95de02

patches similar to that have had to be applied to a number of ports now, to work around the issues we have with Xcode 11's clang.

If you are willing to try doing the leg work yourself, please try applying a similar fix to mono to see if it also addresses the issues here ?

comment:9 Changed 5 years ago by mf2k (Frank Schima)

Cc: MarcusCalhoun-Lopez removed
Owner: set to MarcusCalhoun-Lopez
Status: newassigned

comment:10 Changed 4 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Upgrade to the latest version of mono fixed the problem for me.
However, I cannot find a reason why this is so.
If this does not work for others, please feel free to reopen the ticket.

comment:11 Changed 4 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: fixed
Status: assignedclosed

In 693f659888bce6d34abe2ba63fdc6416c76eee61/macports-ports (master):

mono: update version 6.0.0.319->6.4.0.198

Fixes #59427

Note: See TracTickets for help on using tickets.