#30262 closed defect (fixed)
qt4-mac fails on 10.7 with llvm-gcc-4.2
| Reported by: | marc.schlaich@… | Owned by: | michaelld (Michael Dickens) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.99 |
| Keywords: | lion | Cc: | nerdling (Jeremy Lavergne), jamesfmarshall@…, raimue (Rainer Müller), st.hennig@…, dsdale24@…, maehne (Torsten Maehne) |
| Port: | qt4-mac |
Description
I cannot compile Qt after updated to OS X 10.7 Lion.
Attachments (4)
Change History (31)
Changed 13 years ago by marc.schlaich@…
comment:1 Changed 13 years ago by jmroot (Joshua Root)
| Owner: | changed from macports-tickets@… to michaelld@… |
|---|
comment:2 Changed 13 years ago by marc.schlaich@…
Same error with a new MacPorts installation and 2.0.0-rc1
comment:3 Changed 13 years ago by jmroot (Joshua Root)
| Keywords: | lion added |
|---|---|
| Version: | 1.9.2 → 1.9.99 |
Changed 13 years ago by jamesfmarshall@…
| Attachment: | main.2.log added |
|---|
Much longer main.log file after proper migration to Lion.
comment:4 follow-up: 5 Changed 13 years ago by jamesfmarshall@…
After having the same problem, I followed the instructions on the Migration page, deleted all my ports, cleaned everything, selfupdated MacPorts 2.0.0, and then reinstalled all my ports - except qt4-mac. I saw no problems with the building or installation of any of those ports. I then did a sudo port install qt4-mac. The build process ran for at least half an hour before the build failed. The main.log is attached. For whatever reason, this main.log is much, much longer than the one generated the first time I tried to build and install qt4-mac. I have no idea whether this is significant, but it seems odd. In any event, this much longer main.log file may provide more information of use to solving the problems that prevent qt4-mac from building under Lion.
comment:6 Changed 13 years ago by michaelld (Michael Dickens)
Thank y'all for the logs; please compress the bigger ones first next time.
I'm traveling right now, and probably won't be able to download / install Lion until early August. So, unless someone can come up with a patch in the interim, folks will just have to be patient for a few weeks.
comment:8 Changed 13 years ago by carsomyr@…
Hi all, after some searching, I found out that 4.8.0-beta1 is indeed compatible with Lion! Please find Portfile patch archive attached for transitioning from qt4-mac @4.7.3 to qt4-mac-devel @4.8.0-beta1. I built it, and no problems so far. Some tweaks are necessary:
- The CoreWLAN patch needs to be updated further.
- Some names and lines of code have been shuffled around.
comment:10 Changed 13 years ago by nerdling (Jeremy Lavergne)
Download and unarchive the file in a simple place, such as your home directory. Then do something similar to the following in the Terminal:
Run cd port dir qt4-mac-devel
If necessary, become root (sudo -s)
Run patch < ~/patch-4.7.3-to-4.8.0-beta1.diff
Run port install qt4-mac-devel
Be sure to leave root.
comment:11 Changed 13 years ago by pixilla (Bradley Giesbrecht)
To download the patch I have to change /attachment/ to /raw-attachment/ in the url patch-4.7.3-to-4.8.0-beta1.tgz
comment:12 Changed 13 years ago by jamesfmarshall@…
It's the "something similar" that gets me every time. :-)
Changed 13 years ago by carsomyr@…
| Attachment: | patch-4.7.3-to-4.8.0-beta1.tgz added |
|---|
The port patch archive to transition from 4.7.3 to 4.8.0-beta1 (second submission).
Changed 13 years ago by raimue (Rainer Müller)
| Attachment: | qt4-mac-lion.diff added |
|---|
Fix build error related to NSDragOperation
comment:15 Changed 13 years ago by raimue (Rainer Müller)
| Cc: | raimue@… added |
|---|---|
| Summary: | qt4-mac fails on 10.7 → qt4-mac fails on 10.7 with llvm-gcc-4.2 |
Here is a patch for the error related to NSDragOperation. Unfortunately qt4-mac still didn't compile for me due to the error described in #30271. Michael, may I commit this first patch which allows using llvm-gcc-4.2 and close this ticket?
comment:16 follow-up: 22 Changed 13 years ago by nerdling (Jeremy Lavergne)
GO for it: permission granted in comment 6 ;-)
comment:17 Changed 13 years ago by jamesfmarshall@…
How can we tell when the patch has been applied/committed?
comment:18 follow-up: 19 Changed 13 years ago by nerdling (Jeremy Lavergne)
After a port selfupdate or port sync the port will show as outdated when you do port outdated.
comment:19 Changed 13 years ago by jamesfmarshall@…
Replying to snc@…:
After a
port selfupdateorport syncthe port will show as outdated when you doport outdated.
But I don't have qt4-mac installed because I followed the Migration instructions.
comment:20 Changed 13 years ago by nerdling (Jeremy Lavergne)
Ah, then check port info … periodically, and hopefully the change would be marked in this ticket. Another you can do is go to the browser section of the site and just watch if the Portfile is updated there.
comment:22 Changed 13 years ago by michaelld (Michael Dickens)
Replying to snc@…:
GO for it: permission granted in comment 6 ;-)
What SNC said :) Yes, please do commit, if you haven't already.
comment:23 Changed 13 years ago by raimue (Rainer Müller)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:24 follow-up: 25 Changed 13 years ago by jamesfmarshall@…
Is this the same problem?
https://bugreports.qt.nokia.com//browse/QTBUG-17869
Mike McQuaid commented on QTBUG-20496 (Qt does not compile under OSX Lion or llvm-gcc) saying: This can probable be closed, the merge request has been merged and commit included.
comment:25 Changed 13 years ago by raimue (Rainer Müller)
Replying to jamesfmarshall@…:
Is this the same problem?
No. The linked issue is about running Qt, not about building anything.
Mike McQuaid commented on QTBUG-20496 (Qt does not compile under OSX Lion or llvm-gcc) saying: This can probable be closed, the merge request has been merged and commit included.
As you could have found out reviewing the files added in r81019, this is exactly what I added as a local patch file to the qt4-mac port.
Please remember to cc the maintainer. Are you really using 1.9.2? If so, please first install a newer version such as 2.0.0-rc1.