Opened 4 years ago
Closed 4 years ago
#61747 closed defect (fixed)
Failed to build clang-7.0 on Big Sur
Reported by: | rodmur (Dale Harris) | Owned by: | kencu (Ken) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.4 |
Keywords: | Cc: | ||
Port: | clang-7.0 |
Description
when updating outdated packages, clang-7.0 failed to build with the following error:
---> Configuring clang-7.0 ---> Building clang-7.0 Error: Failed to build clang-7.0: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-7.0/clang-7.0/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. ---> Some of the ports you installed have notes: libomp has the following notes: To use this OpenMP library: * For clang-3.8+, or clang-3.7 with +openmp variant: add "-fopenmp" during compilation / linking. * For clang-3.7 without +openmp variant, use: "-I/opt/local/include/libomp -L/opt/local/lib/libomp -fopenmp"
Attachments (1)
Change History (9)
Changed 4 years ago by rodmur (Dale Harris)
Attachment: | main.log.gz added |
---|
comment:1 Changed 4 years ago by kencu (Ken)
I wasn't really planning on trying to fix clang-7.0 for BigSur. Do you need it for something, or is it just an update from before?
If you don't specifically need it, please uninstall it (and llvm-7.0) and use clang 9.0 ,10, or 11 -- those are all working on Big Sur.
I suppose I should formally block these from installing on BigSur once we sort out exactly what fails where.
comment:2 Changed 4 years ago by kencu (Ken)
Owner: | set to kencu |
---|---|
Status: | new → assigned |
Summary: | Failed to build clang-7.0 → Failed to build clang-7.0 on Big Sur |
comment:3 Changed 4 years ago by rodmur (Dale Harris)
No, I don't really need it. I was just doing a default update. I'll uninstall it.
comment:4 Changed 4 years ago by bnilsson11
I am trying to install Ngspice, and it is dependent on clang-7.0. Consequently, the installation of Ngspice fails on clang-7.0. Should I file a ticket on Ngspice to use clang-9.0 instead?
BN
comment:5 Changed 4 years ago by bnilsson11
I am trying to install Ngspice, and it is dependent on clang-7.0. Consequently, the installation of Ngspice fails on clang-7.0. Should I file a ticket on Ngspice to use clang-9.0 instead?
BN
comment:6 Changed 4 years ago by kencu (Ken)
Oh yes, if there isn't already. We have a newer mechanism for calling in libomp that is more resilient that what ngspice is doing.
I'd suggest you edit the Portfile to use clang-11, 10, or 9.0 on BigSur while we fix that.
Or don't use openmp for now.
comment:7 Changed 4 years ago by kencu (Ken)
Here you go: <https://github.com/macports/macports-ports/pull/9492>
fixes the openmp part, and also bumps it up to the current version 33.
go ahead and check out that commit, or we'll wait 72h and if no response from maintainer, we'll push this.
comment:8 Changed 4 years ago by kencu (Ken)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
ngspice was updated to use the current base openmp defaulting.
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-7.0/clang-7.0/main.log gziped