Summary: | devel/qt5-qmake: Qmake-Qt5 uses clang for linking instead of gcc/g++ specified in Netbeans toolchain | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | nulluse <info> | ||||
Component: | Individual Port(s) | Assignee: | freebsd-kde (group) <kde> | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Many People | CC: | adridg, loise, tcberner, w.schwarzenfeld | ||||
Priority: | --- | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
nulluse
2016-04-15 00:04:45 UTC
Created attachment 169326 [details]
qt-Debug.mk
Apparently the attached file, generated by qmake-qt5, contains link command that uses clang instead of gcc/g++ specified in Netbeans C++ tool chain:
LINK = clang++
LFLAGS = -pthread -Wl,-rpath,/usr/local/lib
For some reason FreeBSD port of Qt5 has qmake that wants to use a different tool.
Additional info: After blowing away PCBSD 10.3 and installing FreeBSD 10.1 instead the bug is still there. This will always be the case as long as you use a qt build on 10.x which uses clang by default, so qmake will be using the mkspecs for clang in any qt-related builds on 10.3. Can you specify your netbeans build environment setup how to reproduce the process until you use Qt5 ? Feedback timeout? Feedback timeout; if there's an underlying issue it is that Qt (qmake) uses the mkspecs to set up the toolchain, and the default toolchain is set when Qt is compiled. You can change toolchains for Qt by changing QMAKESPEC or passing -spec to qmake when it generates the makefile. However, that's independent of things like CC and CXX in the environment: right now, Qt5 knows about "clang" and "gcc" and none of the suffixed versions. For GCC using architectures Qt/Qmake will now chose gcc${GCC_DEFAULT} -- if you need/want to use the same work around on a clang-architecture, you could fiddle a bit in qt-dist.mk to get the same fix. Please reopen if this is still important. mfg Tobias |