#40852 closed defect (fixed)
qt4-mac does not build on OS X 10.9 Mavericks or later
| Reported by: | kolyosick@… | Owned by: | michaelld (Michael Dickens) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.99 |
| Keywords: | mavericks | Cc: | greger.cronquist@…, nerdling (Jeremy Lavergne), soehn@…, mamoll (Mark Moll), barrettsa@…, tomasz@…, stromnov (Andrey Stromnov), cmutel (Chris Mutel), kurtjaeke@…, macports.org@…, soriyath@…, sam.cox144@…, jamesfmarshall@…, macports@…, sgrewe (Stefan Grewe), d@…, macports@…, fondacio@…, BSeppke (Benjamin Seppke), devernay (Frédéric Devernay), bountin (Martin Prebio), jere@…, macports.org@…, wichert@…, carlesfernandez (Carles Fernandez), dhoese@…, robink@…, izonov@…, 24hesk@…, feliks.kluzniak@…, egon.geerardyn@…, carmine.ventre@…, patrick.sizun@…, tristancollins (Tristan Collins), jrblevin@…, shamardin@…, wintermute_77@…, brad.null@…, peter@…, tiasus@…, sck-nogas (Scott C. Kennedy), oliver.bock@…, angleto@…, nintankle@…, axone-zero, dliessi (Davide Liessi), christian@…, alexcoder@…, StanSanderson, mgrants@…, esteban.py.dev@…, cdeil (Christoph Deil), martin@…, an0nym@…, fyu+macports@…, josephwinston (Joseph Winston), xman00@…, diochnos, kolyosick@…, kevleyski@… |
| Port: | qt4-mac |
Description (last modified by mf2k (Frank Schima))
Error: qt4-mac does not build on OS X 10.9 Mavericks or later. Error: org.macports.fetch for port qt4-mac returned: unsupported platform
Attachments (16)
Change History (152)
comment:1 Changed 11 years ago by mf2k (Frank Schima)
| Description: | modified (diff) |
|---|---|
| Keywords: | mavericks added |
| Owner: | changed from macports-tickets@… to michaelld@… |
| Port: | qt4-mac added |
comment:4 Changed 11 years ago by greger.cronquist@…
For me at least, yes with trunk. Apparently homebrew has similar problems, https://github.com/mxcl/homebrew/issues/21000 - they have issues with WebkitLibrary https://bugreports.qt-project.org/browse/QTBUG-32237. If Webkit is indeed a problem, is it possible to make a port variant that doesn't use Webkit until Qt has resolved their issue?
comment:5 Changed 11 years ago by mf2k (Frank Schima)
| Version: | 2.2.0 → 2.2.99 |
|---|
comment:10 Changed 11 years ago by devernay (Frédéric Devernay)
| Cc: | frederic.devernay@… removed |
|---|
Cc Me!
comment:18 Changed 11 years ago by esteban.py.dev@…
I'm wondering if it's i okey to attach:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_qt4-mac/qt4-mac/main.log
file here?
comment:20 Changed 11 years ago by michaelld (Michael Dickens)
Yes, it is OK to attach logs, but PLEASE compress them first. Qt logs get really big!
I've downloaded 10.9 now, but I'm busy through this weekend. Hopefully I can start hacking on Monday. Maybe others (Qt? homebrew?) will have figured out the issues by then :)
comment:21 Changed 11 years ago by markemer (Mark Anderson)
Does upstream care that this is broken or are they focused on Qt5?
comment:22 Changed 11 years ago by michaelld (Michael Dickens)
I don't know if upstream cares about 10.9 compatibility yet, but they continue to work on the 4.8 repository. Oct 24 came a commit "Introduce Windows version 8.1 and detect by checking the version" ...
comment:35 Changed 11 years ago by Veence (Vincent)
Anyhow, Qt5 is not fit for 10.9 either. We’ll have to wait to get fully compatible versions of either one.
comment:40 Changed 11 years ago by BSeppke (Benjamin Seppke)
Replying to kolyosick@…:
Error: qt4-mac does not build on OS X 10.9 Mavericks or later. Error: org.macports.fetch for port qt4-mac returned: unsupported platform
Hi all!
I am not quite sure if this is the right place, maybe I'll also post about my findings at the qt-project-page... The fact that qt4-mac is not working under Mavericks is disgusting, since nearly everything I use and build has a dependency to this port :(
It took me a few hours and ugly source code crawling to isolate and fix the errors, which cause the build errors ot qt-4(.8.5)-mac:
- The exections inside the portfile for 10.8: I made the Portfile to accept the OS X Version and also applied patch-src_corelib_corelib.pro.diff in case of darwin 13.
- Errors of Qt not recognizing OS X 10.9: In order to introduce OS X 10.9, I aded a patch to update src/corelib/qglobal.h
- Errors of plugins: The plugin "beaver" uses an old Interface to access the CoreWiFi-Services. These have been "updated" in 10.9, which means that a lot of former deprecated functions have been deleted. I extended the existing patchfile to (hopefully correctly) use the new CoreWiFi-api.
- Errors of 3rdparty-modules: The 3rdparty-module CLucene causes a compiler error under the CLang-Version, which comes with OS X 10.9 (Apple Clang 5.0). Luckily, this bug is widely known, so I found a quick fix and wrote another patch-file.
I updated the PortSystem to 2.2.1 today - the system itself is build from source under my MacBook with OS X 10.9.
After all the patches mentioned above, I was able to successfully compile qt4-mac. I will append all the neccessary patches and the new version of the portfile after posting this. And I'd highly appreciate, if anyone could also test these, too.
Best wishes,
Benjamin
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_3rdparty_clucene_src_CLucene_search_FieldCacheImpl.cpp.diff added |
|---|
patch for CLucence at 10.9
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_corelib_global_qglobal.h.diff added |
|---|
patch for promoting OS X 10.9 at Qt's internal config
Changed 11 years ago by BSeppke (Benjamin Seppke)
proposed new Portfile for qt4-mac and Mac OS X 10.9 Maverics
comment:41 Changed 11 years ago by mf2k (Frank Schima)
Please instead attach a unified diff of the Portfile vs. trunk.
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | Portfile.2.diff added |
|---|
diff between current and proposed Portfile
comment:42 Changed 11 years ago by BSeppke (Benjamin Seppke)
However, I should admit that webkit does not compile with these fixes. You should, for a first test, add -no-webkit, as it is done in the second Portfile.2.diff file.
After the sucessful build, I encountered another error, due to a missing directory:
./destroot/opt/local/tests/qt4
I added this folder before staging and the destrooting, installing and activating went well.
I'll have a look on the errors that arise when building webkit tomorrow.
comment:43 Changed 11 years ago by devernay (Frédéric Devernay)
| Cc: | frederic.devernay@… added |
|---|
Cc Me!
comment:46 Changed 11 years ago by michaelld (Michael Dickens)
Thanks, Benjamin! I'll create an external 10.9 boot drive tomorrow & start from scractch installing MacPorts. I've got a few 10.9 issues already in my queue, and Qt4 is the biggie ... so, I'm glad to have someone else hacking on it already. Keep the updates coming!
comment:49 Changed 11 years ago by carlesfernandez (Carles Fernandez)
| Cc: | carles.fernandez@… added |
|---|
Cc Me!
comment:57 Changed 11 years ago by BSeppke (Benjamin Seppke)
Next update (last one for today, and hopefully nearly finished): Today I tested the former proposed steps a bit further and have to tell you some things:
- The former patch for bearer is not functional. It compiles but if called, it will not work. This is due to the change from NSArray to NSSet. NSSet does not support objectAtIndex.. When i call PyQt for example, I get 2013-10-28 23:08:33.714 Python[15064:890f] -[NSSetI objectAtIndex:]: unrecognized selector sent to instance 0x7ffcd67af970. I'll take a closer look on this issue tomorrow.
- Today I worked on the enabling of WebKit to be built under 10.9. So far, it took more hours than I imagined, but it finally works for me now. Nearly all the errors are quite easy to fix, although there are quite a lot of them. I'll attach all the five new patch-files to this thread after this posting. This also requires a new static WebKit library, which I borrowed from https://codereview.qt-project.org/#change,69328 . I'll also append that lib to this thread
- Unfortunately, I could not fix one error in src/3rdparty/webkit/Source/WebCore/platform/Timer.cpp. It is just about the two calls "pop_heap" and "push_heap" calls, which result in strange c++11 errors during compilation. Instead I "fixed it" by commenting the lines out, just to see if it's working afterwards. Thus, the patch indicating this file is more ore less a temporary workaround and should *not* be considered as a patch.
To conclude, if I see it right, we only need to fix two issues now: The bearer Objective-C-code for the new CoreWLAN-api and the c++ code for the WebKit's WebCore/platform/Timer.cpp c++ file. I hope to get that done by tomorrow, but I'd highly appreciate and be thankful for any kind of support or further testing.
Best wishes, Benjamin
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_3rdparty_webkit_Source_WebCore_platform_network_qt_QNetworkReplyHandler.cpp.diff added |
|---|
WebKit and Mac OS X 10.9 patch
Changed 11 years ago by BSeppke (Benjamin Seppke)
WebKit and Mac OS X 10.9 patch
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_3rdparty_webkit_Source_WebKit_qt_WebCoreSupport_NotificationPresenterClientQt.cpp.diff added |
|---|
WebKit and Mac OS X 10.9 patch
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | Portfile.3.diff added |
|---|
Portfile diff with first attempt of WebKit support
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | libWebKitSystemInterfaceMavericks.a added |
|---|
WebKit static lib for OS X 10.9 (from https://codereview.qt-project.org/#change,69328)
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_plugins_bearer_corewlan_qcorewlanengine.mm.diff added |
|---|
New "now working at 10.9" patchfile for the Objective Code in bearer
comment:69 Changed 11 years ago by BSeppke (Benjamin Seppke)
Finished! It took me another day and some deeper insights in newer versions of the WebKit library for solving the platform/Timer.cpp issue. To do so, there are two patches needed. One for the Timer.cpp and one for the header Timer.h. After adding these patches to the new Protfile, Qt4 compiles without any error or warnings pushed to the macports-terminal-screen.
After this posting I will update all necessary patchfiles at this issue. The final Portfile-diff will also be added.
Enjoy this and feel free to try Qt4.8 on your own machine / running 10.9 or not... Maybe, after some more testing, we can push thes bunch of patches towards the port
Best wishes, Benjamin
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_3rdparty_webkit_Source_WebKit_qt_QtWebKit.pro.diff added |
|---|
WebKit and Mac OS X 10.9 patch
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_3rdparty_webkit_Source_WebCore_platform_Timer.cpp.2.diff added |
|---|
WebKit and Mac OS X 10.9 patch
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_3rdparty_webkit_Source_WebCore_platform_Timer.cpp.diff added |
|---|
WebKit and Mac OS X 10.9 patch
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | patch-src_3rdparty_webkit_Source_WebCore_platform_Timer.h.diff added |
|---|
WebKit and Mac OS X 10.9 patch
Changed 11 years ago by BSeppke (Benjamin Seppke)
| Attachment: | Portfile.diff added |
|---|
Final patch for Portfile using all the new patches to build under 10.9
comment:70 Changed 11 years ago by michaelld (Michael Dickens)
My 10.9 boot is coming along, and I will get to qt4-mac very soon. I don't think I would have had the time to do this myself, so: Thank you very much, Benjamin!
comment:71 Changed 11 years ago by evandrix (Lee Wei Yeong)
Looking forward to the new 10.9-compatible qt4-mac, thanks!
comment:73 follow-up: 74 Changed 11 years ago by BSeppke (Benjamin Seppke)
Since I got the first mail, which was like: I didn't work with your latest patch-files:
You need to download all 10 patchfiles:
- patch-src_3rdparty_clucene_src_CLucene_search_FieldCacheImpl.cpp.diff
- patch-src_corelib_global_qglobal.h.diff
- patch-src_3rdparty_webkit_Source_WebCore_platform_network_qt_QNetworkReplyHandler.cpp.diff
- patch-src_3rdparty_webkit_Source_WebKit_qt_Api_qgraphicswebview.cpp.diff
- patch-src_3rdparty_webkit_Source_WebKit_qt_WebCoreSupport_NotificationPresenterClientQt.cpp.diff
- libWebKitSystemInterfaceMavericks.a
- patch-src_plugins_bearer_corewlan_qcorewlanengine.mm.diff
- patch-src_3rdparty_webkit_Source_WebKit_qt_QtWebKit.pro.diff
- patch-src_3rdparty_webkit_Source_WebCore_platform_Timer.cpp.diff
- patch-src_3rdparty_webkit_Source_WebCore_platform_Timer.h.diff
and copy them to "aqua/qt4-mac/files".
Then apply the latest Portfile.diff to the Portfile. Then you may try "port install qt4-mac"...
comment:74 Changed 11 years ago by jprosser (Justin Prosser)
I just finished building and installing qt4-mac and that ran through successfully with all 10 patchfiles and the Portfile change as directed. Though I had to edit the Portfile initially before anything would happen thanks to the original pre-fetch condition, so I commented that out to get started.
comment:89 Changed 11 years ago by michaelld (Michael Dickens)
Attaching the Qt Project's fix for coreWLAN, commit ef98098ef34581a473a885badea63d415bcf64f3 from 2013-10-27. Yes, I'm working on this right now :) I'm going to use their patch, since it will be an official change in some future Qt4 release. But, thank you, Benjamin, for the hard work you put in to create your patch.
Changed 11 years ago by michaelld (Michael Dickens)
| Attachment: | qt-project-fix-coreWLAN.diff added |
|---|
comment:91 Changed 11 years ago by michaelld (Michael Dickens)
I just checked in r112811 with this ticket's changes. It should be live by ~5:30 PM/US/ET.
comment:92 follow-up: 93 Changed 11 years ago by wkerzendorf (Wolfgang Kerzendorf)
I just tried it and it doesn't seem to quite work yet
Applying patches to qt4-mac Error: org.macports.patch for port qt4-mac returned: error copying "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/aqua/qt4-mac/files/libWebKitSystemInterfaceMavericks.a": no such file or directory Please see the log file for port qt4-mac for details:
But thanks for all the effort, mavericks is out for only a little while and most things work! Great effort!
comment:93 follow-up: 94 Changed 11 years ago by barrettsa@…
Same here. The end of the log file shows:
:error:patch org.macports.patch for port qt4-mac returned: error copying "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/aqua/qt4-mac/files/libWebKitSystemInterfaceMavericks.a": no such file or directory
:debug:patch Error code: NONE
:debug:patch Backtrace: error copying "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/aqua/qt4-mac/files/libWebKitSystemInterfaceMavericks.a": no such file or directory
while executing
"$post $targetname"
Indeed the libWebKitSystemInterfaceMavericks.a is nowhere to be found.
comment:94 Changed 11 years ago by jeabraham
Replying to barrettsa@…:
Same here. The end of the log file shows:
:error:patch org.macports.patch for port qt4-mac returned: error copying "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/aqua/qt4-mac/files/libWebKitSystemInterfaceMavericks.a": no such file or directory :debug:patch Error code: NONE :debug:patch Backtrace: error copying "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/aqua/qt4-mac/files/libWebKitSystemInterfaceMavericks.a": no such file or directory while executing "$post $targetname"Indeed the libWebKitSystemInterfaceMavericks.a is nowhere to be found.
Same here. libWebKitSystemInterfaceMavericks.a missing. Thanks for the work everyone.
comment:95 Changed 11 years ago by StanSanderson
Sad to see I’m not the only one missing the libWebKit… But thanks for the work!
comment:96 Changed 11 years ago by michaelld (Michael Dickens)
Is anyone having success? Please try:
sudo port clean qt4-mac sudo port selfupdate sudo port install qt4-mac
also, if you do
ls -lAF `port dir qt4-mac`/files/libWeb*
do you see the library ("libWebKitSystemInterfaceMavericks.a")? It should be 535752 bytes.
comment:97 Changed 11 years ago by bountin (Martin Prebio)
After cleaning:
$ ls -lAF `port dir qt4-mac`/files/lib* total 32 -rwxr-xr-x 1 root wheel 1203 Jul 15 18:03 library_path.test* -rw-r--r-- 1 root wheel 16 Jul 15 18:03 library_path_lib.c -rw-r--r-- 1 root wheel 23 Jul 15 18:03 library_path_lib.h -rw-r--r-- 1 root wheel 83 Jul 15 18:03 library_path_test.c
:(
I've put the log file here: https://gist.github.com/anonymous/7274214
comment:98 Changed 11 years ago by StanSanderson
exactly the same results here, looking for lib* . The libWebKitSysteminterfaceMavericks.a file is missing.
comment:99 follow-up: 100 Changed 11 years ago by michaelld (Michael Dickens)
Sorry y'all. The library is checked in, but for some reason it isn't being downloaded. You can download it directly and place it into qt4-mac/files while I/we figure out what's going on.
Can someone do "sudo port -d sync" and post the output of it? I use the SVN trunk for my work, so if you're not using that then maybe the sync method is showing a warning or something.
comment:100 Changed 11 years ago by barrettsa@…
Replying to michaelld@…:
Can someone do "sudo port -d sync" and post the output of it? I use the SVN trunk for my work, so if you're not using that then maybe the sync method is showing a warning or something.
Here you go:
$ sudo port -d sync Password: DEBUG: Copying /Users/scott/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences ---> Updating the ports tree Synchronizing local ports tree from rsync://rsync.macports.org/release/tarballs/ports.tar DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/ports.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs receiving file list ... done ports.tar sent 53405 bytes received 112 bytes 11892.67 bytes/sec total size is 57978880 speedup is 1083.37 DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/ports.tar.rmd160 /opt/local/var/macports/sources/rsync.macports.org/release/tarballs receiving file list ... done ports.tar.rmd160 sent 64 bytes received 117 bytes 120.67 bytes/sec total size is 512 speedup is 2.83 DEBUG: successful verification with key /opt/local/share/macports/macports-pubkey.pem DEBUG: /usr/bin/tar -C /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/tmp -xf /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports.tar Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports Total number of ports parsed: 0 Ports successfully parsed: 0 Ports failed: 0 Up-to-date ports skipped: 17811
comment:101 Changed 11 years ago by michaelld (Michael Dickens)
OK; thanks. The file libWebKitSysteminterfaceMavericks.a is indeed not part of the rsync tarball. I'll query the list as to what the best way is to get binary files like this one inserted into a build.
comment:103 Changed 11 years ago by michaelld (Michael Dickens)
It is part of WebKit. I know nothing more. I can set up the Portfile to download it from WebKit directly, or MacPorts directly. Sounds like this is what I need to do.
comment:104 Changed 11 years ago by michaelld (Michael Dickens)
Done in r112821. I included both download locations; this works for me.
comment:105 Changed 11 years ago by jmroot (Joshua Root)
Even assuming it's under one of the licenses used by most of WebKit (which you really shouldn't), BSD and LGPL licenses require you to reproduce the relevant copyright notices and license terms. If you do not do this in the port, we are distributing the qt4-mac binary in violation of the license.
comment:108 Changed 11 years ago by diochnos
After solving temporarily the problem with libWebKit... there is a new problem:
1 out of 1 hunk ignored -- saving rejects to file config.tests/unix/compile.test.rej Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_qt4-mac/qt4-mac/work/qt-everywhere-opensource-src-4.8.5" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/aqua/qt4-mac/files/patch-config.tests_unix_compile.test.diff' Exit code: 1 Error: org.macports.patch for port qt4-mac returned: command execution failed Warning: targets not executed for qt4-mac: org.macports.destroot org.macports.patch org.macports.configure org.macports.build
And the relevant part from the log:
:info:patch 1 out of 1 hunk ignored -- saving rejects to file config.tests/unix/compile.test.rej :info:patch Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_aqua_qt4-mac/qt4-mac/work/qt-everywhere-opensource-src-4.8.5" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/aqua/qt4-mac/files/patch-config.tests_unix_compile.test.diff' :info:patch Exit code: 1 :error:patch org.macports.patch for port qt4-mac returned: command execution failed
comment:109 follow-ups: 110 113 Changed 11 years ago by michaelld (Michael Dickens)
Try:
sudo port clean qt4-mac sudo port install qt4-mac
and see if that takes care of the patch issue.
comment:110 Changed 11 years ago by barrettsa@…
I've successfully installed qt4-mac. Thanks for your diligence!
comment:112 Changed 11 years ago by StanSanderson
Thanks - successful upgrade of qt4-mac + a number of files on which it depended.
comment:113 Changed 11 years ago by diochnos
Replying to michaelld@…:
Try:
sudo port clean qt4-mac sudo port install qt4-macand see if that takes care of the patch issue.
As others were reporting positively I was hoping this would be the case for me as well. However, the above two were not enough. New errors this time:
:info:build 1 warning and 3 errors generated.
:info:build make[2]: *** [src/shared/CMakeFiles/clucene-shared.dir/CLucene/config/gunichartables.o] Error 1
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_clucene/clucene/work/clucene-core-2.3.3.4'
:info:build make[1]: *** [src/shared/CMakeFiles/clucene-shared.dir/all] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_clucene/clucene/work/clucene-core-2.3.3.4'
:info:build make: *** [all] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_clucene/clucene/work/clucene-core-2.3.3.4'
:info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_clucene/clucene/work/clucene-core-2.3.3.4" && /usr/bin/make -j2 -w all
:info:build Exit code: 2
:error:build org.macports.build for port clucene returned: command execution failed
:debug:build Error code: CHILDSTATUS 57154 2
:debug:build Backtrace: command execution failed
while executing
"system -nice 0 $fullcmdstring"
("eval" body line 1)
invoked from within
"eval system $notty $nice \$fullcmdstring"
invoked from within
"command_exec build"
(procedure "portbuild::build_main" line 8)
invoked from within
"$procedure $targetname"
:info:build Warning: targets not executed for clucene: org.macports.destroot org.macports.build
:notice:build Please see the log file for port clucene for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_clucene/clucene/main.log
Moreover, a little bit further above I noticed this part of the output:
---> Unable to uninstall qt4-mac @4.8.5_0, the following ports depend on it: ---> automoc @0.9.88_3 ---> phonon @4.6.0_0 ---> attica @0.4.0_0 ---> qjson @0.7.1_1 ---> dbusmenu-qt @0.9.0_0 ---> grantlee @0.2.0_0 ---> qca @2.0.3_0 ---> shared-desktop-ontologies @0.9.0_0 ---> soprano @2.7.4_0 ---> kdelibs4 @4.8.3_2 ---> oxygen-icons @4.8.3_0 ---> kate @4.8.3_0 ---> qimageblitz @0.0.6_0 ---> poppler @0.20.3_0+qt4+quartz ---> okular @4.8.3_1 ---> kde4-kile @2.1.2_0 ---> kde4-runtime @4.8.3_2 ---> akonadi @1.7.2_0 ---> prison @1.0_0 ---> kdepimlibs4 @4.8.3_0 ---> kde4-baseapps @4.8.3_0 ---> poppler @0.20.4_0+qt4+quartz ---> kdelibs4 @4.8.3_3 ---> kdepimlibs4 @4.8.3_1 ---> automoc @0.9.88_4 ---> soprano @2.8.0_1 ---> akonadi @1.8.1_0 ---> poppler @0.20.5_0+qt4+quartz ---> shared-desktop-ontologies @0.10.0_0 ---> kdelibs4 @4.9.3_0 ---> oxygen-icons @4.9.3_0 ---> kate @4.9.3_0 ---> kdepimlibs4 @4.9.3_0 ---> kactivities @4.9.3_0 ---> nepomuk-core @4.9.3_0 ---> kde4-runtime @4.9.3_0 ---> kde4-baseapps @4.9.3_0 ---> okular @4.9.3_0 ---> kde4-kile @2.1.3_0 ---> soprano @2.9.0_0 ---> qt4-mac-mysql5-plugin @4.8.4_0 ---> akonadi @1.9.1_0+mysql5 ---> dbusmenu-qt @0.9.2_0 ---> poppler @0.22.2_0+qt4+quartz ---> grantlee @0.3.0_0 ---> kdelibs4 @4.10.1_0 ---> kactivities @4.10.1_0 ---> oxygen-icons @4.10.1_0 ---> kate @4.10.1_2 ---> nepomuk-core @4.10.1_0 ---> kdepimlibs4 @4.10.1_0 ---> kde4-runtime @4.10.1_1 ---> nepomuk-widgets @4.10.1_0 ---> kde4-baseapps @4.10.1_1 ---> okular @4.10.1_0 ---> phonon @4.6.0_1 ---> soprano @2.9.2_0 ---> qt4-mac-mysql5-plugin @4.8.5_0 ---> akonadi @1.9.2_0+mysql5 ---> poppler @0.24.0_0+qt4+quartz ---> qca @2.0.3_1 ---> kdelibs4 @4.10.5_0 ---> kactivities @4.10.5_0 ---> oxygen-icons @4.10.5_0 ---> kate @4.10.5_0 ---> nepomuk-core @4.10.5_0 ---> kdepimlibs4 @4.10.5_0 ---> kde4-runtime @4.10.5_0 ---> nepomuk-widgets @4.10.5_0 ---> kde4-baseapps @4.10.5_0 ---> okular @4.10.5_0 Warning: Uninstall forced. Proceeding despite dependencies. ---> Deactivating qt4-mac @4.8.5_0 ---> Unable to deactivate qt4-mac @4.8.5_0, the following ports depend on it: ---> attica @0.4.0_0 ---> qjson @0.7.1_1 ---> qimageblitz @0.0.6_0 ---> prison @1.0_0 ---> automoc @0.9.88_4 ---> shared-desktop-ontologies @0.10.0_0 ---> kde4-kile @2.1.3_0 ---> dbusmenu-qt @0.9.2_0 ---> grantlee @0.3.0_0 ---> phonon @4.6.0_1 ---> soprano @2.9.2_0 ---> qt4-mac-mysql5-plugin @4.8.5_0 ---> akonadi @1.9.2_0+mysql5 ---> poppler @0.24.0_0+qt4+quartz ---> qca @2.0.3_1 ---> kdelibs4 @4.10.5_0 ---> kactivities @4.10.5_0 ---> oxygen-icons @4.10.5_0 ---> kate @4.10.5_0 ---> nepomuk-core @4.10.5_0 ---> kdepimlibs4 @4.10.5_0 ---> kde4-runtime @4.10.5_0 ---> nepomuk-widgets @4.10.5_0 ---> kde4-baseapps @4.10.5_0 ---> okular @4.10.5_0 Warning: Deactivate forced. Proceeding despite dependencies. ---> Cleaning qt4-mac ---> Removing work directory for qt4-mac ---> Uninstalling qt4-mac @4.8.5_0 ---> Cleaning qt4-mac ---> Removing work directory for qt4-mac ---> Computing dependencies for qt4-mac. ---> Installing qt4-mac @4.8.5_0
I guess I have lots of dependencies...
Thanks anyway!
comment:114 follow-up: 120 Changed 11 years ago by michaelld (Michael Dickens)
@diochnos: can you attach the log file (compressed) for me to look through? If you're not sure, you can easily recreate it:
sudo port clean qt4-mac sudo port build qt4-mac
and when qt4-mac errors out, grab the log file, compress it, and post that. If qt4-mac builds, then try
sudo port install qt4-mac
and see if it completes.
comment:115 follow-up: 118 Changed 11 years ago by wintermute_77@…
I was able to successfully build qt4-mac under 10.9 here.
comment:116 Changed 11 years ago by michaelld (Michael Dickens)
Thanks for the positive feedback; you're welcome, and BIG thanks for Benjamin for his help! I think we're mostly there, but if you have issues with qt4-mac and 10.9: I highly recommend doing the full:
sudo port clean qt4-mac sudo port selfupdate sudo port install qt4-mac
to see if that clears up the issue; and if not then please post a compressed log file to this ticket and we'll work on figuring out the issues.
comment:118 Changed 11 years ago by evandrix (Lee Wei Yeong)
Replying to wintermute_77@…:
I was able to successfully build qt4-mac under 10.9 here.
same experience here. thanks for all the effort!
comment:120 Changed 11 years ago by diochnos
Replying to michaelld@…:
@diochnos: can you attach the log file (compressed) for me to look through? If you're not sure, you can easily recreate it:
sudo port clean qt4-mac sudo port build qt4-macand when qt4-mac errors out, grab the log file, compress it, and post that. If qt4-mac builds, then try
sudo port install qt4-macand see if it completes.
Thanks. It did complete this time, so I am pretty sure that when I will attempt to upgrade all the outdated the problem may arise elsewhere. Thanks! :)
comment:121 follow-up: 123 Changed 11 years ago by BSeppke (Benjamin Seppke)
Just a little (final) comment from my side: I'm very happy about all the success messages. It was absolute worth the work to make qt4-mac compiling under 10.9 Mavericks. Regarding myself, a successful Qt4 is a *need* for my working/development environment. Since we are very high ranked on Goolge w.r.t. "Qt4 mac 10.9 Mavericks", let's hope, that the Qt-guys are looking at our patches and include them in (hopefully comming) Qt4.8.6. The need for adaption might be smaller than this time, as the development versions of e.g. WebKit are quite easier to patch and compile under Mac OS X 10.9.
I hope you all enjoy the use of Qt4 at Mavericks!
Have a nice weekend and best wishes,
Benjamin
comment:123 Changed 11 years ago by emaguarino@…
Replying to benjamin.seppke@…:
Just a little (final) comment from my side: I'm very happy about all the success messages. It was absolute worth the work to make qt4-mac compiling under 10.9 Mavericks. Regarding myself, a successful Qt4 is a *need* for my working/development environment. Since we are very high ranked on Goolge w.r.t. "Qt4 mac 10.9 Mavericks", let's hope, that the Qt-guys are looking at our patches and include them in (hopefully comming) Qt4.8.6. The need for adaption might be smaller than this time, as the development versions of e.g. WebKit are quite easier to patch and compile under Mac OS X 10.9.
I hope you all enjoy the use of Qt4 at Mavericks!
Have a nice weekend and best wishes,
Benjamin
Thank you for your time!!!
comment:124 Changed 11 years ago by michaelld (Michael Dickens)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:125 Changed 11 years ago by kevleyski@…
| Cc: | kevleyski@… added |
|---|
comment:128 Changed 11 years ago by jnielsendotnet
Hopefully this will save someone else some time. Even after all the fixes (documented here) from the latest version of the port, I was getting this error:
DEBUG: configure phase started at Mon Nov 11 15:30:22 MST 2013 ---> Configuring qt4-mac DEBUG: Using compiler 'Xcode Clang' DEBUG: Executing proc-pre-org.macports.configure-configure-0 Error: org.macports.configure for port qt4-mac returned: incomplete operator "=" in expression "${MINOR} = "9"" DEBUG: Error code: NONE DEBUG: Backtrace: incomplete operator "=" in expression "${MINOR} = "9""
while executing
"$pre $targetname"
After I ran "sudo xcode-select -s /Library/Developer/CommandLineTools" and ran "port clean qt4-mac" I was able to build the port successfully (previously the path was set to /Applications/Xcode.app/Contents/Developer). Don't forget to run "xcode-select --install" as well. Thanks for all the work done on this!
comment:129 Changed 11 years ago by jamesfmarshall@…
I seem to have command line tools in both /Library/Developer/CommandLineTools and /Applications/Xcode.app/Contents/Developer .
Is that a problem? Why prefer those in one location over the other? The default locations appears to be the package contents.
comment:130 follow-up: 132 Changed 11 years ago by michaelld (Michael Dickens)
I have no "/Library/Developer/CommandLineTools", but I do have "/Applications/Xcode.app/Contents/Developer". I wonder if maybe the former should be removed? /Library is generally for stuff that you install yourself, so maybe this is some leftover from a prior OSX install?
comment:132 Changed 11 years ago by graziosi.angelo@…
Replying to michaelld@…:
I have no "/Library/Developer/CommandLineTools", but I do have "/Applications/Xcode.app/Contents/Developer". I wonder if maybe the former should be removed? /Library is generally for stuff that you install yourself, so maybe this is some leftover from a prior OSX install?
---
The things, here, are a little confusing for me... (I have not installed anything in /Library myself)
Leaving aside the fact that yesterday I have update Xcode to 5.0.2 (5A3005) and "sudo xcode-select --install" does not yet allow me to update command line tools because the server is off, I have /Library/Developer/CommandLineTools which contains, for example,
$ ls -lrt /Library/Developer/CommandLineTools/usr/bin/clang* lrwxr-xr-x 1 root admin 5 10 Nov 10:52 /Library/Developer/CommandLineTools/usr/bin/clang++ -> clang -rwxr-xr-x 1 root admin 29381728 10 Nov 10:52 /Library/Developer/CommandLineTools/usr/bin/clang $ /Library/Developer/CommandLineTools/usr/bin/clang -v Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) Target: x86_64-apple-darwin13.0.0 Thread model: posix
but I have also /Applications/Xcode.app/Contents/Developer with
$ ls -lrt /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang* lrwxr-xr-x 1 root wheel 5 18 Set 23:07 /Applications/Xcode.app//Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -> clang -rwxr-xr-x 1 root wheel 29381728 24 Ott 23:15 /Applications/Xcode.app//Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang $ /Applications/Xcode.app//Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -v Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) Target: x86_64-apple-darwin13.0.0 Thread model: posix
Notice the two different timestamp for clang but it is the same compiler..
So, what is the right folder? Is my Xcode installation what is to be expected? If not, how to "sanitize" it?
Thanks,
Angelo.
comment:133 follow-up: 134 Changed 11 years ago by jamesfmarshall@…
I deleted everything and reinstalled Xcode 5.0.2 from the App Store. The command line tools are now installed internally as part of the package contents of Xcode. The command line tools are installed separately and externally in /Library/Developer/CommandLineTools only when one executes xcode-select --install. For a simple setup with only the latest version of Xcode, 5.0.2, it seems unnecessary to run xcode-select --install to get the command line tools.
comment:134 Changed 11 years ago by graziosi.angelo@…
Replying to jamesfmarshall@…:
I deleted everything and reinstalled Xcode 5.0.2 from the App Store. The command line tools are now installed internally as part of the package contents of Xcode. The command line tools are installed separately and externally in /Library/Developer/CommandLineTools only when one executes xcode-select --install. For a simple setup with only the latest version of Xcode, 5.0.2, it seems unnecessary to run xcode-select --install to get the command line tools.
---
This was the solution I had in mind...
May you explain (detailing) what you have deleted and how?
Many thanks,
Angelo.
comment:135 Changed 11 years ago by michaelld (Michael Dickens)
Thanks for the info, @jamesfmarshall. I just updated to 5.0.2, started up Xcode, which prompted me about installing components to which I clicked OK. Then, I went into Preferences -> Downloads, and had it update all components including the command-line tools. Back to X11 in a terminal, there is nothing in /Library/Developer. If I do "xcode-select --print-path", I get back "/Applications/Xcode.app/Contents/Developer"; further, there is no "--install" option in xcode-select any longer. So, my advice to others is to run "xcode-select --print-path" and see what it shows. If it is not "/Applications/Xcode.app/Contents/Developer" then use "xcode-select --switch /Applications/Xcode.app/Contents/Developer" to correctly set the path, and then go in and delete whatever the alternative path was (e.g., "cd /Library/Developer && sudo rm -rf *"). You might have to reinstall Xcode after doing this, but I'll guess that Xcode's select, like MacPorts, just "does the right thing" most of the time so it'll be OK. But, once you've set the correct Xcode path to use, I think all well be well.
comment:136 Changed 9 months ago by slarew
| Cc: | slarew removed |
|---|
In the future, please use WikiFormatting, fill in the Port field and Cc the port maintainers (
port info --maintainers qt4-mac).