Cannot install qt4-mac on Mac OSX 10.6.4

[sa00044@…]

Hello everyone. I have been trying to install Amarok on my Macbook but so far nothing good has happened. I have come across many installation problems that were resolved with selfupdate However, now it seems the problem is a bit more tricky.

For some reason, I can't install qt4-mac. I always receive the following error: Error: Target org.macports.build returned: shell command failed Log for qt4-mac is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_qt4-mac/main.log Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade automoc failed To report a bug, see <​http://guide.macports.org/#project.tickets>

Here is the log. Any help would be highly appreciated.

Thank you!

[sa00044@…]

Error Log

[michaelld (Michael Dickens)]

This is the same issue as tickets #20199 and #25320 - roughly: a conflicting port is installed & qt4-mac is including a header file from that port instead of an internal one because the -I and CPATH are not set correctly. I'll be checking in changes to qt4-mac "real soon now" that address this issue. I'm closing this ticket as duplicate, but I'll post back here once the changes are in place so that you know.

[sa00044@…]

Replying to michaelld@…:

This is the same issue as tickets #20199 and #25320 - roughly: a conflicting port is installed & qt4-mac is including a header file from that port instead of an internal one because the -I and CPATH are not set correctly. I'll be checking in changes to qt4-mac "real soon now" that address this issue. I'm closing this ticket as duplicate, but I'll post back here once the changes are in place so that you know.

---

Thank you. To be honest, I checked those two tickets, #20199 and #25320 before posting, but since I can only describe myself as a simple user, I could not spot that I was talking about the same thing more or less. I have absolutely no idea as to what all these lines of code mean and is really difficult for me to spot any differences or similarities. Hope that was no problem, posting again for the same matter.

Thank you for posting back and hope to hear from you soon. I really need to make Amarok run on my Macbook :-)

[michaelld (Michael Dickens)]

No; no problem. We get duplicates all the time & it's really no surprise since a lot of folks catch the same issue. It's sort of "crowd debugging". I'm glad that you checked; you're doing better than many folks! I'm testing out Amarok right now, to make sure it works (now maybe 1/4 way through my list of ports to check). More soon.

[michaelld (Michael Dickens)]

Fixed in r69277 .

[sa00044@…]

Replying to michaelld@…:

Fixed in r69277 .

Ok, I know that this might sound stupid but, what should I do now? Should I just try once again to install qt4-mac, or do I need to do something else first?

[sa00044@…]

Replying to sa00044@…:

Replying to michaelld@…:

Fixed in r69277 .

Ok, I know that this might sound stupid but, what should I do now? Should I just try once again to install qt4-mac, or do I need to do something else first?

Maybe that was indeed stupid of me to ask. I have made sudo port selfupdate and then sudo port upgrade outdated and is currently building qt4-mac, after having updated cmake and qt4_select. I will come back as soon as I have any results.

Thanks michaelld !!!

[sa00044@…]

Error: Target org.macports.build returned: shell command failed Log for qt4-mac is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_qt4-mac/main.log Error: Unable to upgrade port: 1 To report a bug, see <​http://guide.macports.org/#project.tickets>

I have set the topic to "reopen" since it seems that it hasn't been solved yet.

And here is my new log. Any ideas???

[sa00044@…]

New Log for qt4-mac

[sa00044@…]

Sorry I had to attach a .zip file but the log was 4.6 MB !!!

[michaelld (Michael Dickens)]

Ug; do you have 'kdelibs3' installed? Can you do "port provides /opt/local/include/KURL.h" and let me know what that returns. Your issue is the same as in ticket #20199, which I thought I had corrected. Sigh. We'll work it out. I also forgot a ${destroot} in the select file installation, so you'll want to do "sudo port sync" to make sure you get that change.

[michaelld (Michael Dickens)]

The issue is that "kdelibs3" (according to others) provides "/opt/local/include/KURL.h", as does "qt4-mac/src/3rdparty/webkit/WebCore/platform", but this last directory isn't included in the header search path during that part of the compile and hence the 'wrong' KURL.h is used. So, this is an upstream problem but one we can correct by patching either the resulting Makefile or the input .pro file. I'll work on this issue later today & also check Qt's bug tickets. If you have time, can you try "sudo port build qt4-mac-devel" & see if the latest beta release still has this issue? I know compiling qt4 takes a long time ...

[sa00044@…]

Replying to michaelld@…:

Ug; do you have 'kdelibs3' installed? Can you do "port provides /opt/local/include/KURL.h" and let me know what that returns. Your issue is the same as in ticket #20199, which I thought I had corrected. Sigh. We'll work it out. I also forgot a ${destroot} in the select file installation, so you'll want to do "sudo port sync" to make sure you get that change.

Here is what I get when I do port provides /opt/local/include/KURL.h:

nikolas-laptop:~ Nikolas$ port provides /opt/local/include/KURL.h

/opt/local/include/KURL.h is not provided by a MacPorts port.

[sa00044@…]

Replying to michaelld@…:

The issue is that "kdelibs3" (according to others) provides "/opt/local/include/KURL.h", as does "qt4-mac/src/3rdparty/webkit/WebCore/platform", but this last directory isn't included in the header search path during that part of the compile and hence the 'wrong' KURL.h is used. So, this is an upstream problem but one we can correct by patching either the resulting Makefile or the input .pro file. I'll work on this issue later today & also check Qt's bug tickets. If you have time, can you try "sudo port build qt4-mac-devel" & see if the latest beta release still has this issue? I know compiling qt4 takes a long time ...

Now doing sudo port build qt4-mac-devel.

Will let you know as soon as I have results. Thanks again!

[michaelld (Michael Dickens)]

Well, no matter the outcome if I were you I'd certainly do:

sudo rm /opt/local/include/KURL.h

since it doesn't belong with MacPorts any longer. That said, I'll still get the header include path fixed tonight. Thanks again for your feedback.

[sa00044@…]

Here is the log of qt4-ma-devel (unfortunately failed)

I also did did sudo rm /opt/local/include/KURL.h , but only this morning, after failure of qt4-mac-devel

[sa00044@…]

qt4-mac-devel log

[michaelld (Michael Dickens)]

Thanks for the log. Same issue. I'm tracking it down right now, but removing that file will at least fix the immediate problem for you. You'll also want to comment out the qt4-mac[-devel] Portfile line 11 that should now read:

# select.group        ${select_group}

and then destroot & post-destroot should work now for both qt4-mac* ports. If you still have qt4-mac built, you could try:

sudo port -o install qt4-mac

(with whatever variant you started the process), and hopefully that'll work. Subtle stuff going on here!

[michaelld (Michael Dickens)]

I just checked in changes to qt4-mac[-devel] that hopefully take care of the other ticket on it (#25459). If you've removed the KURL.h file, then you should be good to go now. I know that qt4-mac take forever to compile, but could you please do:

sudo port sync
sudo port clean qt4-mac
sudo port install qt4-mac

with whatever variant to qt4-mac you like (or none), and let me know how it goes. I've got my fingers crossed :)

[Themanwithoutaplan]

I don't have KURL.h, I have an up to date version of MacPorts and I'm still getting the configure error. Log will be attached.

[Themanwithoutaplan]

Configure log

[Themanwithoutaplan]

Cc Me!

[sa00044@…]

Replying to michaelld@…:

I just checked in changes to qt4-mac[-devel] that hopefully take care of the other ticket on it (#25459). If you've removed the KURL.h file, then you should be good to go now. I know that qt4-mac take forever to compile, but could you please do:

sudo port sync
sudo port clean qt4-mac
sudo port install qt4-mac

with whatever variant to qt4-mac you like (or none), and let me know how it goes. I've got my fingers crossed :)

All right, I am just beginning to do, all that stuff that you instructed:

sudo port sync sudo port clean qt4-mac sudo port install qt4-mac

Will come back soon with good news (I hope) :-)

[michaelld (Michael Dickens)]

@Charlie.clark: If you do "ls /Developer/SDKs" what does it return?

[Themanwithoutaplan]

@Michael

MacOSX10.6.sdk

[michaelld (Michael Dickens)]

Thanks! That's what I suspected. The issue is that qt4-mac uses the 10.4 SDK by default and needs to be told otherwise for 10.5 or 10.6; if I don't upgrade the SDK, some Qt features don't compile or work. So, I choose the "minimal" upgrade -- to 10.5. But, if you don't have the 10.5 SDK installed then this upgrade doesn't work -- and, so, using the 10.6 SDK would probably make sense in your case. I'll work on it; I think there's a way to verify which SDK is available.

[michaelld (Michael Dickens)]

The original part of this ticket is actually a duplicate of #20199 (which was closed by me, thinking I'd fixed it). So, I'm going to close this ticket & reopen that one.

@sa00044 : You can choose to add yourself as "cc" to that other ticket; I would assume if you removed the KURL.h file then compiling qt4-mac will work & hence you might not be interested in this issue any longer.

@charlie.clark : I'm opening a new ticket with your issue since it's separate from this one's original issue, and I'll add you as "CC" to it.

[sa00044@…]

Replying to michaelld@…:

The original part of this ticket is actually a duplicate of #20199 (which was closed by me, thinking I'd fixed it). So, I'm going to close this ticket & reopen that one.

@sa00044 : You can choose to add yourself as "cc" to that other ticket; I would assume if you removed the KURL.h file then compiling qt4-mac will work & hence you might not be interested in this issue any longer.

@charlie.clark : I'm opening a new ticket with your issue since it's separate from this one's original issue, and I'll add you as "CC" to it.

Good News!!!

qt4-mac successfully installed!!!

I am now going on to try to install amarok. Once again, thank you very much for your help. You've been great!

[michaelld (Michael Dickens)]

Great! You're welcome. While I was getting qt4-mac update, I had to work over all the ports that use qt4-mac, which includes amarok. So, you'll find that amarok was updated to the latest version. I hope it installs easily and works well for you.

[sa00044@…]

Replying to michaelld@…:

Great! You're welcome. While I was getting qt4-mac update, I had to work over all the ports that use qt4-mac, which includes amarok. So, you'll find that amarok was updated to the latest version. I hope it installs easily and works well for you.

Well, I am afraid that amarok does not install. I have opened a new tickek #25489. Can you check it out?

[sa00044@…]

Replying to sa00044@…:

Replying to michaelld@…:

Great! You're welcome. While I was getting qt4-mac update, I had to work over all the ports that use qt4-mac, which includes amarok. So, you'll find that amarok was updated to the latest version. I hope it installs easily and works well for you.

Well, I am afraid that amarok does not install. I have opened a new tickek #25489. Can you check it out?

So, it seems that you already have. Sorry for my previous message and thank you for your super fast reply!