Opened 8 months ago
Closed 8 months ago
#73011 closed defect (duplicate)
Failure to build ghc with macOS Tahoe, missing (or bad) C libraries: m, dl, ffi
| Reported by: | JoachimRose | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | ghc |
Description
Starting with a clean (new) install of MacPorts on macOS Tahoe
Then trying to install Root6 with Jupyter option : sudo port install root6 +jupyter
This apparently relies on ghc as a prerequisite, but the build fails.
---> Fetching archive for ghc ---> Attempting to fetch ghc-9.12.2_1.darwin_25.arm64.tbz2 from https://packages.macports.org/ghc ---> Attempting to fetch ghc-9.12.2_1.darwin_25.arm64.tbz2 from https://mse.uk.packages.macports.org/ghc ---> Attempting to fetch ghc-9.12.2_1.darwin_25.arm64.tbz2 from https://fra.de.packages.macports.org/ghc ---> Building ghc Error: Failed to build ghc: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_ghc/ghc/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port root6 failed
Excerpt from the log file, with a reference to "Missing (or bad) C libraries: m, dl, ffi".
:info:build Reading parameters from :info:build /opt/local/var/macports/build/ghc-c7a81590/work/ghc-9.12.2/_build/stage1/rts/build/rts.buildinfo :info:build Error: [Cabal-4345] :info:build Missing dependencies on foreign libraries: :info:build * Missing (or bad) C libraries: m, dl, ffi :info:build This problem can usually be solved by installing the system packages that provide these libraries (you may need the "-dev" versions). If the libraries are already installed but in a non-standard location then you can use the flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.If the library files do exist, it may contain errors that are caught by the C compiler at the preprocessing stage. In this case you can re-run 'Setup configure' with the verbosity flag -v3 to see the error messages.
There seems to be a similar open ticket : https://trac.macports.org/ticket/72773
Change History (1)
comment:1 Changed 8 months ago by reneeotten (Renee Otten)
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |

has duplicate 72773