[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 15:26:47 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:11 cave-canem]:
 > {{{
 > port select --summary | rg "(Name|====|clang|llvm)"
 > Name       Selected         Options
 > ====       ========         =======
 > clang      mp-clang-16      mp-clang-10 mp-clang-11 mp-clang-13 mp-
 clang-14 mp-clang-15 mp-clang-16 mp-clang-3.7 mp-clang-5.0 mp-clang-9.0
 none
 > llvm       mp-llvm-16       mp-llvm-10 mp-llvm-11 mp-llvm-12 mp-llvm-13
 mp-llvm-14 mp-llvm-15 mp-llvm-16 mp-llvm-3.7 mp-llvm-5.0 mp-llvm-9.0 mp-
 llvm-devel none
 > }}}

 Okay, that matches with what I saw in the logs. Bear in mind that by
 selecting defaults, this takes precedence over which Clang version is
 chosen for a given port. And that increases your chances of build errors,
 like what you're experiencing here.

 Net-Net, don't do that.

 Can you please select `none` for both `clang` and `llvm`, run `sudo port
 clean libheif` to clean the logs, and try your upgrade again?

-- 
Ticket URL: <https://trac.macports.org/ticket/67404#comment:14>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list