[MacPorts] #67404: libheif @1.16.1_0: error: non-portable path to file '<DAV1D/xxx.h>' and '<AOM/xxx.h>'
MacPorts
noreply at macports.org
Thu May 11 13:13:21 UTC 2023
#67404: libheif @1.16.1_0: error: non-portable path to file '<DAV1D/xxx.h>' and
'<AOM/xxx.h>'
-------------------------+-----------------------
Reporter: cave-canem | Owner: mascguy
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.8.1
Resolution: | Keywords: Mavericks
Port: libheif |
-------------------------+-----------------------
Comment (by mascguy):
Replying to [comment:9 MarcusCalhoun-Lopez]:
> I cannot reproduce these errors, but I do not have access to a case-
sensitive file system.
There's an easy way to fix that, by creating either a RAM disk - or other
temporary storage - for the MacPorts build area (formatted as case-
sensitive):
{{{
$ sudo bash -c 'dev=$(hdiutil attach -nomount ram://16777216) ; newfs_hfs
-s -v "MacPorts-RamDisk-8G" ${dev} ; mount -t hfs ${dev}
/opt/local/var/macports/build'
}}}
Inspiration taken from open enhancement request: comment:7:issue:32261.
I've been using this approach for many months, and it works well. It's
also allowed me to proactively catch legitimate instances of case mis-
mismatches prior to committing, so it's worthwhile in-general.
Even with that in play though, I'm not able to reproduce this issue
either. (Nor did this occur on any of the buildbots.) So I suspect it's
related to a newer version of Clang.
--
Ticket URL: <https://trac.macports.org/ticket/67404#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list