<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Feb 11, 2021, at 3:33 PM, John Hoyt <<a href="mailto:john.hoyt@gmail.com" class="">john.hoyt@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">BTW - I tracked down the libjpeg issue I had in my build to a local configuration issue (which I hope my asible updates will resolve). Per Craig's suggestion (thanks once again Craig!), I looked into what ports still had libjpeg vs libjpeg-turbo dependencies. qt5-webkit (our crash culprit) was the only one hanging onto libjpeg. Telling macports to uninstall libjpeg then issuing a "port rev-upgrade" triggered a recompile of qt5-webkit and everything worked from there. </span></div></blockquote></div><br class=""><div class="">John, you’ve actually spotted a problem with the MacPorts packaging of qt5-qtwebkit. We had not identified libjpeg as a dependency and therefore didn’t change it to libjpeg-turbo in the mass switch. I’ll follow up on that.</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Craig</div><div class=""><br class=""></div></body></html>