Re: [kde-freebsd] ports/181932: www/qt4-webkit: fatal error: 'ext/atomicity.h' file not found (on CLANG only)
Synopsis: www/qt4-webkit: fatal error: 'ext/atomicity.h' file not found (on CLANG only) Responsible-Changed-From-To: freebsd-ports-bugs-kde Responsible-Changed-By: edwin Responsible-Changed-When: Sun Sep 8 11:10:09 UTC 2013 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=181932 ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181913: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous
On Sep 8, 2013, at 08:14, O. Hartmann ohart...@zedat.fu-berlin.de wrote: On Sat, 7 Sep 2013 22:49:54 GMT rak...@freebsd.org wrote: Synopsis: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous State-Changed-From-To: open-patched State-Changed-By: rakuco State-Changed-When: Sat Sep 7 22:47:43 UTC 2013 State-Changed-Why: I don't think the previous version worked. From your description, it looks like you've switched to building with libc++ whereas libstdc++ was being used before. The upcoming Qt 4.8.5 plus a few patches which only made it to 4.8.6 (but we've backported) will finally make Qt build with libc++. We've just sent an exp-run request for Qt 4.8.5, and will hopefully fix all these errors once it is committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=181913 I build the world/kernel since early this year with CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++11 in /etc/src.conf. I do not use those flags in /etc/make.conf! /etc/src.conf is supposed to target ONLY the /usr/src world, not the ports - this is as I interpret the man page for /etc/src.conf and it would be logical. But this rule/thinking seems to be broken by some includes from /usr/ports/Mk ingredients. Since r255321, -stdlib=libc++ is effectively the default, at least when you haven't set gcc as the default compiler. So it also applies to ports, which unavoidably will lead to a bit of fallout. My personal experience is that most C++-based ports compile fine with libc++ instead of libstdc++, except for a few that rely on internal libstdc++ details. However, -std=c++11 is *not* yet the default, and C++11 has different rules here and there, so some ports might fail to compile due to this. For some ports, too much hacking may be required to make them work with C++11. So in case of trouble, try removing -std=, or setting it to different values (c++0x, c++98, gnu++98, etc), to get the port to compile. Note the base system should have no problems with -std=c++11, so please continue to use the option in src.conf, and report any problems if you encounter them, so we can fix them. :-) -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181913: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous
08.09.2013 10:14, O. Hartmann пишет: I can assure that I didn't switch anything to build the ports but rebuilding world and then restarting building. Something must have changed since then in the logic of how libc++ slipped in instead of of libstdc++. What I did was a make delete-old-files, which deleted several GNU gcc stuff on all CURRENT boxes. I did not see that any lib got killed after I tried make delete-old-libs. And I did not check whether libstdc++ is still being built. Yes, recently gcc was switched off by default at CURRENT, so libc++ is used both for the system and ports. There are many other occasions where now c++ errors occur and I guess those ports need to be reported in one by one via PR? Guess so. Preferrable with a patch. ;-) -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181913: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous
On Sun, 8 Sep 2013 14:57:01 +0200 Dimitry Andric d...@freebsd.org wrote: On Sep 8, 2013, at 08:14, O. Hartmann ohart...@zedat.fu-berlin.de wrote: On Sat, 7 Sep 2013 22:49:54 GMT rak...@freebsd.org wrote: Synopsis: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous State-Changed-From-To: open-patched State-Changed-By: rakuco State-Changed-When: Sat Sep 7 22:47:43 UTC 2013 State-Changed-Why: I don't think the previous version worked. From your description, it looks like you've switched to building with libc++ whereas libstdc++ was being used before. The upcoming Qt 4.8.5 plus a few patches which only made it to 4.8.6 (but we've backported) will finally make Qt build with libc++. We've just sent an exp-run request for Qt 4.8.5, and will hopefully fix all these errors once it is committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=181913 I build the world/kernel since early this year with CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++11 in /etc/src.conf. I do not use those flags in /etc/make.conf! /etc/src.conf is supposed to target ONLY the /usr/src world, not the ports - this is as I interpret the man page for /etc/src.conf and it would be logical. But this rule/thinking seems to be broken by some includes from /usr/ports/Mk ingredients. Since r255321, -stdlib=libc++ is effectively the default, at least when you haven't set gcc as the default compiler. So it also applies to ports, which unavoidably will lead to a bit of fallout. My personal experience is that most C++-based ports compile fine with libc++ instead of libstdc++, except for a few that rely on internal libstdc++ details. However, -std=c++11 is *not* yet the default, and C++11 has different rules here and there, so some ports might fail to compile due to this. For some ports, too much hacking may be required to make them work with C++11. So in case of trouble, try removing -std=, or setting it to different values (c++0x, c++98, gnu++98, etc), to get the port to compile. Note the base system should have no problems with -std=c++11, so please continue to use the option in src.conf, and report any problems if you encounter them, so we can fix them. :-) -Dimitry Hello Dimitry. I ONLY use -std=c++11 in /etc/src.conf. The base system had never problems so far since I use it. In /etc/make.conf, I avoid it. But, and this is obviously a logical incosistency, the ports system includes also /etc/src.conf, and I consider /etc/src.conf as base system only as the man page suggests. But the discussion has already been on the list. Somewhere in the basd.*.mk files, /etc/src.conf is included. And I guess therefore it comes to problems. Oliver signature.asc Description: PGP signature ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181913: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous
On Sat, 7 Sep 2013 22:49:54 GMT rak...@freebsd.org wrote: Synopsis: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous State-Changed-From-To: open-patched State-Changed-By: rakuco State-Changed-When: Sat Sep 7 22:47:43 UTC 2013 State-Changed-Why: I don't think the previous version worked. From your description, it looks like you've switched to building with libc++ whereas libstdc++ was being used before. The upcoming Qt 4.8.5 plus a few patches which only made it to 4.8.6 (but we've backported) will finally make Qt build with libc++. We've just sent an exp-run request for Qt 4.8.5, and will hopefully fix all these errors once it is committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=181913 I build the world/kernel since early this year with CXXFLAGS+= -stdlib=libc++ CXXFLAGS+= -std=c++11 in /etc/src.conf. I do not use those flags in /etc/make.conf! /etc/src.conf is supposed to target ONLY the /usr/src world, not the ports - this is as I interpret the man page for /etc/src.conf and it would be logical. But this rule/thinking seems to be broken by some includes from /usr/ports/Mk ingredients. I can assure that I didn't switch anything to build the ports but rebuilding world and then restarting building. Something must have changed since then in the logic of how libc++ slipped in instead of of libstdc++. What I did was a make delete-old-files, which deleted several GNU gcc stuff on all CURRENT boxes. I did not see that any lib got killed after I tried make delete-old-libs. And I did not check whether libstdc++ is still being built. There are many other occasions where now c++ errors occur and I guess those ports need to be reported in one by one via PR? signature.asc Description: PGP signature ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181935: x11/libkonq: ERROR: cmake/modules/FindKDE4Internal.cmake not found in Call Stack (most recent call first): CMakeLists.txt:12 (find_package)
The following reply was made to PR ports/181935; it has been noted by GNATS. From: Raphael Kubo da Costa rak...@freebsd.org To: bug-follo...@freebsd.org Cc: O. Hartmann ohart...@zedat.fu-berlin.de Subject: Re: ports/181935: x11/libkonq: ERROR: cmake/modules/FindKDE4Internal.cmake not found in Call Stack (most recent call first): CMakeLists.txt:12 (find_package) Date: Sun, 08 Sep 2013 21:54:29 +0300 Has x11/kdelibs4 been installed correctly? ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181335: [PATCH] devel/qmake4: Fix port test and Tinderbox, trim ${LN}
The following reply was made to PR ports/181335; it has been noted by GNATS.
From: Raphael Kubo da Costa rak...@freebsd.org
To: bug-follo...@freebsd.org
Cc: nemy...@freebsd.org
Subject: Re: ports/181335: [PATCH] devel/qmake4: Fix port test and Tinderbox,
trim ${LN}
Date: Sun, 08 Sep 2013 21:52:21 +0300
+nemysis, hopefully I got his nick correctly after two attempts :-)
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181952: devel/kdevelop-kde4: CMake Error at /usr/local/share/cmake/Modules/FindKDE4.cmake:98 (message): ERROR: cmake/modules/FindKDE4Internal.cmake not found in Call Stack (mos
Synopsis: devel/kdevelop-kde4: CMake Error at /usr/local/share/cmake/Modules/FindKDE4.cmake:98 (message): ERROR: cmake/modules/FindKDE4Internal.cmake not found in Call Stack (most recent call first): CMakeLists.txt:12 (find_package) Responsible-Changed-From-To: freebsd-ports-bugs-kde Responsible-Changed-By: edwin Responsible-Changed-When: Sun Sep 8 21:10:08 UTC 2013 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=181952 ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181913: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous
Synopsis: devel/qt4-script: /usr/include/c++/v1/type_traits:3175:22: error: call to 'swap' is ambiguous State-Changed-From-To: patched-closed State-Changed-By: rakuco State-Changed-When: Mon Sep 9 00:48:20 UTC 2013 State-Changed-Why: In the end I didn't wait for the exp-run, otherwise Qt and the world would be broken. Fixed in r326562 and r326688. http://www.freebsd.org/cgi/query-pr.cgi?pr=181913 ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] ports/181932: commit references a PR
The following reply was made to PR ports/181932; it has been noted by GNATS. From: dfil...@freebsd.org (dfilter service) To: bug-follo...@freebsd.org Cc: Subject: Re: ports/181932: commit references a PR Date: Mon, 9 Sep 2013 00:53:47 + (UTC) Author: rakuco Date: Mon Sep 9 00:53:36 2013 New Revision: 326777 URL: http://svnweb.freebsd.org/changeset/ports/326777 Log: Add a ton of patches needed to get the port building with libc++. One of them is a patch I got into Qt some time ago, but patch-libcxx is a collection of commits to WebKit itself (and a few changes of mine) that never got downstream Qt's copy of WebKit. Some good soul with free time should work on porting qtwebkit-23 [1], which contains a much more up-to-date WebKit checkout. [1] https://blogs.kde.org/2013/07/17/qtwebkit-232-and-qtwebkit-qt-51 PR: ports/181932 Added: head/www/qt4-webkit/files/patch-libcxx (contents, props changed) head/www/qt4-webkit/files/patch-src__3rdparty__webkit__Source__JavaScriptCore__wtf__Atomics.h (contents, props changed) Added: head/www/qt4-webkit/files/patch-libcxx == --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/www/qt4-webkit/files/patch-libcxx Mon Sep 9 00:53:36 2013 (r326777) @@ -0,0 +1,983 @@ +Several upstream (as in WebKit itself) commits that fix the build with libc++, +plus a few additional changes made only for the port (the OS(FREEBSD) part for +time_t). Some of those commits had to be edited because they did not apply +cleanly to the ancient WebKit checkout present in Qt. + +Upstream commit messages: + + +r86529 | aba...@webkit.org | 2011-05-16 09:30:58 +0300 (Mon, 16 May 2011) | 7 lines + +2011-05-15 Adam Barth aba...@webkit.org + +Attempt to fix Qt build. (Strict PassOwnPtr fix.) + +* dom/XMLDocumentParserQt.cpp: +(WebCore::XMLDocumentParser::doEnd): + + +r86530 | aba...@webkit.org | 2011-05-16 09:36:56 +0300 (Mon, 16 May 2011) | 13 lines + +2011-05-15 Adam Barth aba...@webkit.org + +Attempt to fix Qt build. (Strict PassOwnPtr fix.) + +* platform/network/qt/QNetworkReplyHandler.cpp: +(WebCore::QNetworkReplyWrapper::release): +(WebCore::QNetworkReplyWrapper::receiveMetaData): +(WebCore::QNetworkReplyWrapper::receiveSniffedMIMEType): +(WebCore::QNetworkReplyHandler::release): +(WebCore::QNetworkReplyHandler::finish): +(WebCore::QNetworkReplyHandler::redirect): +(WebCore::QNetworkReplyHandler::start): + + +r86531 | aba...@webkit.org | 2011-05-16 09:41:08 +0300 (Mon, 16 May 2011) | 7 lines + +2011-05-15 Adam Barth aba...@webkit.org + +Attempt to fix Qt build. (Strict PassOwnPtr fix.) + +* platform/text/qt/TextCodecQt.cpp: +(WebCore::newTextCodecQt): + + +r86532 | aba...@webkit.org | 2011-05-16 09:46:33 +0300 (Mon, 16 May 2011) | 8 lines + +2011-05-15 Adam Barth aba...@webkit.org + +Attempt to fix Qt build. (Strict PassOwnPtr fix.) + +* platform/graphics/qt/GraphicsLayerQt.cpp: +(WebCore::GraphicsLayerQt::GraphicsLayerQt): +(WebCore::GraphicsLayer::create): + + + +r86533 | aba...@webkit.org | 2011-05-16 09:52:23 +0300 (Mon, 16 May 2011) | 10 lines + +2011-05-15 Adam Barth aba...@webkit.org + +Attempt to fix the Qt build. (Strict PassOwnPtr fix.) + +* Api/qgraphicswebview.cpp: +(QGraphicsWebViewPrivate::detachCurrentPage): +(QGraphicsWebView::setPage): +* Api/qwebpage.cpp: +(QWebPage::setView): + + +r86537 | aba...@webkit.org | 2011-05-16 10:24:01 +0300 (Mon, 16 May 2011) | 41 lines + +2011-05-16 Adam Barth aba...@webkit.org + +[Qt] QtPlatformPlugin create methods should use PassOwnPtr +https://bugs.webkit.org/show_bug.cgi?id=60873 + +This change is slightly more than a build fix because the patch kind of +spidered a bit while I was trying to fix the build the right way. +Hopefully nothing here is controversial. + +* Api/qwebpage.cpp: +(QWebPagePrivate::adjustPointForClicking): +* WebCoreSupport/ChromeClientQt.cpp: +(WebCore::ChromeClientQt::createSelectPopup): +* WebCoreSupport/FullScreenVideoQt.cpp: +(WebCore::FullScreenVideoQt::FullScreenVideoQt): +(WebCore::FullScreenVideoQt::~FullScreenVideoQt): +*
Re: [kde-freebsd] ports/181921: [exp-run] Update Qt to 4.8.5
New patch available at http://people.freebsd.org/~rakuco/exp-runs/qt-4.8.5-v2.diff ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
