[MacPorts] #42788: freetype: ignoring file /opt/local/lib/libharfbuzz.dylib, file was built for x86_64 which is not the architecture being linked (i386): /opt/local/lib/libharfbuzz.dylib (was: freetype link error: "warning: ignoring file /opt/local/lib/libharfbuzz.dylib")

[MacPorts]

#42788: freetype: ignoring file /opt/local/lib/libharfbuzz.dylib, file was built
for x86_64 which is not the architecture being linked (i386):
/opt/local/lib/libharfbuzz.dylib
-----------------------+--------------------------
  Reporter:  pdm@…     |      Owner:  ryandesign@…
      Type:  defect    |     Status:  reopened
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.2.1
Resolution:            |   Keywords:
      Port:  freetype  |
-----------------------+--------------------------
Changes (by ryandesign@…):

 * cc: quentin.riffard@… (added)
 * status:  closed => reopened
 * resolution:  invalid =>


Comment:

 Sorry, what I wrote previously was incorrect.

 The filing of duplicate #42817 helped me realize this is not an isolated
 incident. I should have looked closer to realize that it is unexpected
 that freetype is trying to use harfbuzz at all. Harfbuzz support is new in
 freetype 2.5.3, and I hadn't realized that when I committed the update, so
 freetype does not declare a dependency on harfbuzz, so this problem occurs
 when you're trying to build freetype universal but harfbuzz is not
 installed universal.

 In fact, we cannot make freetype depend on harfbuzz because harfbuzz
 already depends on freetype, and MacPorts cannot accommodate circular
 dependencies. So what we must do is force freetype not to use harfbuzz,
 even if it is installed.

-- 
Ticket URL: <https://trac.macports.org/ticket/42788#comment:5>
MacPorts <http://www.macports.org/>
Ports system for OS X