Changes between Initial Version and Version 1 of Ticket #54151, comment 4
- Timestamp:
- May 11, 2017, 6:47:25 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #54151, comment 4
initial v1 20 20 So - yeah - commotion deep in the guts of qt4. Options are to use something like that tricky tricky bit of `sed`'ing Michael used, or to just tell people to install qt4-mac as +universal and be done with it for all ports that might have this issue. 21 21 22 Doesn't look like michaelld actually figured out why it happened sometimes. Just fixed it up after . Must be some reason it occurs in certain ports, of course.22 Doesn't look like michaelld actually figured out why it happened sometimes. Just fixed it up after in that one port. Must be some reason it occurs in certain ports, of course. 23 23 24 24 I installed qt4-mac +universal last year, and so would never see this error, I guess. Seems pretty tempting to just force qt4-mac to be +univeral by default... not the purist thing, to be sure, but heck, qt4-using ports are not going to generate a ton of interest any more.