Opened 5 years ago
Closed 5 years ago
#59068 closed defect (fixed)
carthage @0.33.0_0 build fails with Xcode 11
| Reported by: | i0ntempest | Owned by: | saagarjha (Saagar Jha) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.5.4 |
| Keywords: | xcode11 | Cc: | |
| Port: | carthage |
Description
build log attached
Attachments (2)
Change History (10)
Changed 5 years ago by i0ntempest
comment:1 Changed 5 years ago by mf2k (Frank Schima)
| Cc: | saagarjha removed |
|---|---|
| Owner: | set to saagarjha |
| Status: | new → assigned |
comment:2 Changed 5 years ago by saagarjha (Saagar Jha)
comment:3 Changed 5 years ago by mf2k (Frank Schima)
| Keywords: | xcode11 added |
|---|
comment:4 Changed 5 years ago by saagarjha (Saagar Jha)
Managed to reproduce this once I got around swift build not being able to find my developer tools. It seems like the bug has already been reported in the relevant places: https://bugs.swift.org/browse/SR-11423, https://github.com/Carthage/Carthage/issues/2831. The latter has a "workaround" if you really need this to work, but since this is a Swift bug I think we should wait for them to fix it instead of just applying the band-aid patch.
comment:5 Changed 5 years ago by i0ntempest
It's now throwing another error saying llbuild isn't loaded (with both Xcode 11 and 10.3) but I'm sure that lib is there... Don't know what's going on but think I should report it. Another main log attached.
Changed 5 years ago by i0ntempest
comment:6 Changed 5 years ago by dlamija (Muhammed Ramiza)
carthage @0.33.0_0 with Xcode 11.1 macport 2.6.1; throwing error on installing
---> Staging carthage into destroot Error: Failed to destroot carthage: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_github.com_macports_macports-ports_devel_carthage/carthage/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug.
comment:7 Changed 5 years ago by saagarjha (Saagar Jha)
This is probably the same bug as this one, though we couldn't know without the contents of that log file.
comment:8 Changed 5 years ago by saagarjha (Saagar Jha)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Huh, is that a…Swift compiler crash? We might have to report this upstream. Let me try to see if I can reproduce this on my system.