Changes between Version 1 and Version 2 of Ticket #68655


Ignore:
Timestamp:
Nov 7, 2023, 9:00:57 PM (11 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

A missing binary archive is never the cause of a build failure.

The log shows the real problem was:

:info:build ld: file cannot be mmap()ed, errno=22 path=/Library/Frameworks/rasterlite2.framework in '/Library/Frameworks/rasterlite2.framework'

Having software installed in /Library/Frameworks or /usr/local can interfere with MacPorts. See wiki:FAQ#libraryframeworks. While this problem should be fixed here if possible, I recommend removing what you have installed in /Library/Frameworks and /usr/local to avoid further problems. If you do that, sudo port clean gdal before trying to build it again.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #68655

    • Property Summary changed from gdal fails to build on MacOS Sonoma arm64 to gdal @3.7.3: Build failure when /Library/Frameworks/rasterlite2.framework exists
  • Ticket #68655 – Description

    v1 v2  
    33The first error comes from
    44
     5{{{
    56:info:archivefetch --->  gdal-3.7.3_1+postgresql15+proj9.darwin_23.arm64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
    67:msg:archivefetch --->  Attempting to fetch gdal-3.7.3_1+postgresql15+proj9.darwin_23.arm64.tbz2 from https://packages.macports.org/gdal
     
    1112:debug:archivefetch Fetching archive failed: The requested URL returned error: 404
    1213:debug:archivefetch Privilege de-escalation not attempted as not running as root.
     14}}}