[MacPorts] #57594: dyld error when enabling tests for tk +quartz

[MacPorts]

#57594: dyld error when enabling tests for tk +quartz
--------------------------+---------------------------------
 Reporter:  chrstphrchvz  |      Owner:  MarcusCalhoun-Lopez
     Type:  defect        |     Status:  assigned
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:  2.5.4
 Keywords:                |       Port:  tk
--------------------------+---------------------------------
 Using Tk 8.6.8/8.6.9rc4 on macOS 10.14.1.

 If I manually add `test.run yes` to the `tk` portfile under the `+quartz`
 variant, and run `port -vt test tk +quartz`, there is an error:
 {{{
 DYLD_LIBRARY_PATH="`pwd`:/opt/local/lib:${DYLD_LIBRARY_PATH}"; export
 DYLD_LIBRARY_PATH; …
 dyld: Symbol not found: __cg_jpeg_resync_to_restart
   Referenced from:
 /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
   Expected in: /opt/local/lib/libJPEG.dylib
  in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
 }}}
 ([https://gist.githubusercontent.com/chrstphrchvz/8564f5525d40e28a47c1ee7571ded10a/raw/2d6423e7dbbc504cc3a9f26d47530cf3f6ef3c06/tk869rc4
 -quartz-tests.log full test log])

 I'm guessing `/opt/local/lib/libJPEG.dylib` should instead be
 `/opt/local/lib/libjpeg.dylib` (note this is on a case-insensitive APFS
 volume).

 There have been
 [https://trac.macports.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&resolution=fixed&resolution=invalid&resolution=wontfix&resolution=worksforme&description=~__cg_jpeg_resync_to_restart&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&desc=1&order=id
 tickets] for similar errors on other ports, and one common diagnosis is
 that ports shouldn't use/set `DYLD_LIBRARY_PATH`.

 I'm inclined to think this is a MacPorts-specific issue but haven't ruled
 out it being an upstream issue.

 I am unsure whether tests should be runnable for `+quartz`. My impression
 is they were left out of the portfile mainly because they can't be run for
 the `+x11` variant (since `port` runs tests as the `macports` user, which
 can't access the X11 server).

-- 
Ticket URL: <https://trac.macports.org/ticket/57594>
MacPorts <https://www.macports.org/>
Ports system for macOS