| 3 | | qt511-qtwebkit was broken by the upgrade to turbo-jpeg, and now we find out that something has changed in the past few years, and it can't be rebuilt with the present setup. |
| 4 | | |
| 5 | | Somebody will need to sort out what and why and how to fix it. It's not just your system after all. |
| 6 | | |
| 7 | | I see this up above <https://github.com/macports/macports-ports/commit/00f0c96071a475d968272f70aa4945f111e330b1> so perhaps that is a place to start for whoever it is who will take this issue on. |
| | 3 | qt511-qtwebkit was broken by the upgrade to turbo-jpeg, and now we find out that something has changed in the past few years, and it can't be rebuilt with the present setup. No doubt is the same bison issue as was fixed in qt5-qtwebkit by <https://github.com/macports/macports-ports/commit/00f0c96071a475d968272f70aa4945f111e330b1>. |
