phonon 4.4.2 won't build due to -lphonon not found

[kurthindenburg (Kurt Hindenburg)]

...
:info:build ld: library not found for -lphonon
:info:build collect2: ld returned 1 exit status
:info:build make[3]: *** [../../../build/plugins/phonon_backend/libphonon_qt7.dylib] Error 1

[kurthindenburg (Kurt Hindenburg)]

main.log showing error

[michaelld (Michael Dickens)]

What does the following return:

ls -lAF /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_phonon/work/phonon-4.4.2/build/lib

[kurthindenburg (Kurt Hindenburg)]

Replying to michaelld@…:

What does the following return:

ls -lAF /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_phonon/work/phonon-4.4.2/build/lib

drwxr-xr-x 7 root admin 238 Dec 1 10:59 phonon.framework/ -rw-r--r-- 1 root admin 845 Dec 1 10:59 phonon.la drwxr-xr-x 4 root admin 136 Dec 1 10:59 pkgconfig/

[michaelld (Michael Dickens)]

Arg. I need to update qt4-mac-devel, since it's out of date. Can you do the following:

sudo port clean phonon
sudo port deactivate qt4-mac-devel
sudo port install qt4-mac [+variants]

and then do "sudo port install phonon" which should work now. I don't quite know why 4.4.2 isn't linking -- beyond that it's trying to link to a framework incorrectly -- but using qt4-mac (not -devel) should take care of the issue.

[kurthindenburg (Kurt Hindenburg)]

well that did work; however, I need the headers/etc so I need the qt4-mac-devel port.

[michaelld (Michael Dickens)]

"headers/etc" meaning? Both qt4-mac and qt4-mac-devel install the same (basic) files -- applications, headers, libraries, documents, etc... Maybe do you mean that you need the framework version of Qt, since that's the primary difference between what you have installed (via qt4-mac-devel) and what qt4-mac provides?

Or, do you mean the "header/etc" for phonon? Those are installed in the same way was Qt was installed (framework or separate).

I guess I'm not clear on what exactly it is you require; maybe you can provide clarification?

[kurthindenburg (Kurt Hindenburg)]

I need to compile KDE from svn/trunk (I'm a Konsole Devel).

If I have qt4-mac installed, kdelibs from KDE trunk (not macports) won't compile. It has in the past work w/ qt4-mac-devel.

---

Error w/ qt4-mac installed:

Please set them or make sure they are set and tested correctly in the CMake files:

QT_QT_INCLUDE_DIR

used as include directory in directory /Volumes/ExtraHD/KDE/builds/KDE/apple/trunk/kdelibs/CMakeFiles/CMakeTmp

CMake Error: Internal CMake error, TryCompile configure of cmake failed

CMake Error at cmake/modules/FindKDE4Internal.cmake:1294 (message):

Qt compiled without support for -fvisibility=hidden. This will break

plugins and linking of some applications. Please fix your Qt installation.

Call Stack (most recent call first):

CMakeLists.txt:45 (find_package)

[michaelld (Michael Dickens)]

Ah; I see. I think you're referring to ticket #27524 now, yes? Next revision of Qt I'll have those headers not be deleted, just for folks like you. If you want to do that right now, edit the qt4-mac Portfile, search for "Remove include/Qt" and then delete the "if" statement below it. You'll, unfortunately, have to rebuild all of Qt to get this change -- which is why I haven't checked it in yet. I've got a few open Qt tickets that I'm trying to bunch together into a single revision bump. I really do wish Qt could be modularized -- like building just QtCore, phonon, QtNetwork, and so forth separately. But, we have to put up with what's provided; it would be a real pain to redo the build system so that they are separate.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #27612.

[michaelld (Michael Dickens)]

I don't have kdelibs from the KDE trunk, but we did just check in some changes to the port KDELIBS4 here that help it ignore user-installed system libraries and headers, as well as compile universal. If you require QT_QT_INCLUDE_DIR to be set, then this won't help, probably. But, maybe so?

[michaelld (Michael Dickens)]

I'm closing this ticket as invalid since we've addressed the original issue & your other issue seems to be covered in another ticket. Please do reopen if you do not feel the original issue was addressed, and provide me with more info so that I can address it.