This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Hi all,

I'm trying to compile Wireshark on my Mac, but I do not want to use the provided script to install dependencies. I have my own libraries (MacPorts mostly), and they are working.

The problem is: configure can't find QT. I installed also QT5 in my home directory. it works, but Wireshark's configure ignores it.

Any solution ?

Thanks,

T.

asked 28 Mar '16, 11:19

Tommaso%20Pecorella's gravatar image

Tommaso Peco...
6113
accept rate: 0%

Which version of Qt 5 did you install?

(28 Mar '16, 19:04) Guy Harris ♦♦

What do your PATH and PKG_CONFIG_PATH environment variables look like? Assuming you have Qt 5.6 with the "clang 64-bit" components installed you should have ~/Qt/5.6/clang_64/bin in your PATH and ~/Qt/5.6/clang_64/lib/pkgconfig in your PKG_CONFIG_PATH.

permanent link

answered 28 Mar '16, 12:06

Gerald%20Combs's gravatar image

Gerald Combs ♦♦
3.3k92258
accept rate: 24%

Hi,

both are set (they weren't), but the result is the same.

checking if profile builds must be generated... no checking for GLIB... yes checking for Qt5Core - version >= 5.0.0... no checking for QtCore - version >= 4.7.0... no configure: error: Qt is not available 21:17:47:~/git/wireshark pecos$ env | grep PATH PATH=/opt/local/bin:/opt/local/sbin:/opt/local/libexec/qt4/bin/:/usr/texbin:/Users/pecos/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/MacGPG2/bin:/Library/TeX/texbin:/Users/pecos/Qt/5.6/clang_64/bin PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/X11/lib/pkgconfig:/Users/pecos/Qt/5.6/clang_64/lib/pkgconfig/ 21:17:49:~/git/wireshark pecos$

(28 Mar '16, 12:20) Tommaso Peco...

What does qmake -query print? (and what version of Qt4 is installed in /opt/local?)

(28 Mar '16, 12:27) Gerald Combs ♦♦

For QT4 it is:

01:53:17:~/git/wireshark pecos$ qmake -query
QT_INSTALL_PREFIX:/opt/local/libexec/qt4
QT_INSTALL_DATA:/opt/local/libexec/qt4/share
QT_INSTALL_DOCS:/opt/local/libexec/qt4/share/doc
QT_INSTALL_HEADERS:/opt/local/libexec/qt4/include
QT_INSTALL_LIBS:/opt/local/libexec/qt4/lib
QT_INSTALL_FRAMEWORKS:/opt/local/libexec/qt4/Library/Frameworks
QT_INSTALL_BINS:/opt/local/libexec/qt4/bin
QT_INSTALL_PLUGINS:/opt/local/libexec/qt4/share/plugins
QT_INSTALL_IMPORTS:/opt/local/libexec/qt4/share/imports
QT_INSTALL_TRANSLATIONS:/opt/local/libexec/qt4/share/translations
QT_INSTALL_CONFIGURATION:/opt/local/libexec/qt4/share/sysconf
QT_INSTALL_EXAMPLES:/opt/local/libexec/qt4/share/examples
QT_INSTALL_DEMOS:/opt/local/libexec/qt4/share/demos
QMAKE_MKSPECS:/opt/local/libexec/qt4/share/mkspecs
QMAKE_VERSION:2.01a
QT_VERSION:4.8.7

For QT5:

00:07:02:~/git/wireshark pecos$ ~/Qt/5.6/clang_64/bin/qmake -query
QT_SYSROOT:
QT_INSTALL_PREFIX:/Users/pecos/Qt/5.6/clang_64
QT_INSTALL_ARCHDATA:/Users/pecos/Qt/5.6/clang_64
QT_INSTALL_DATA:/Users/pecos/Qt/5.6/clang_64
QT_INSTALL_DOCS:/Users/pecos/Qt/Docs/Qt-5.6
QT_INSTALL_HEADERS:/Users/pecos/Qt/5.6/clang_64/include
QT_INSTALL_LIBS:/Users/pecos/Qt/5.6/clang_64/lib
QT_INSTALL_LIBEXECS:/Users/pecos/Qt/5.6/clang_64/libexec
QT_INSTALL_BINS:/Users/pecos/Qt/5.6/clang_64/bin
QT_INSTALL_TESTS:/Users/pecos/Qt/5.6/clang_64/tests
QT_INSTALL_PLUGINS:/Users/pecos/Qt/5.6/clang_64/plugins
QT_INSTALL_IMPORTS:/Users/pecos/Qt/5.6/clang_64/imports
QT_INSTALL_QML:/Users/pecos/Qt/5.6/clang_64/qml
QT_INSTALL_TRANSLATIONS:/Users/pecos/Qt/5.6/clang_64/translations
QT_INSTALL_CONFIGURATION:/Users/pecos/Qt/5.6/clang_64
QT_INSTALL_EXAMPLES:/Users/pecos/Qt/Examples/Qt-5.6
QT_INSTALL_DEMOS:/Users/pecos/Qt/Examples/Qt-5.6
QT_HOST_PREFIX:/Users/pecos/Qt/5.6/clang_64
QT_HOST_DATA:/Users/pecos/Qt/5.6/clang_64
QT_HOST_BINS:/Users/pecos/Qt/5.6/clang_64/bin
QT_HOST_LIBS:/Users/pecos/Qt/5.6/clang_64/lib
QMAKE_SPEC:macx-clang
QMAKE_XSPEC:macx-clang
QMAKE_VERSION:3.0
QT_VERSION:5.6.0
(29 Mar '16, 15:08) Tommaso Peco...

Are you using cmake or autotools build? Also, if you are not running macos-setup, then take a look at the output of my script run and adapt it to your environment:

# From the output of macosx-setup.sh
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/Qt5.5.1/5.5/clang_64/lib/pkgconfig:/usr/X11/lib/pkgconfig
export CMAKE_PREFIX_PATH=:/usr/local/Qt5.5.1/5.5/clang_64/lib/cmake
export PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Qt5.5.1/5.5/clang_64/bin
permanent link

answered 28 Mar '16, 13:41

jmayer's gravatar image

jmayer
262
accept rate: 0%

Thanks. I was missing the CMAKE_PREFIX_PATH... but it didn't help either.

make, yes. Autotools, yes. Script adapted, check. Still, configure doesn't find Qt (yes, I tried to run the scripts to fix the bogus QT packageconfig files)

(28 Mar '16, 16:55) Tommaso Peco...

Well, if you are doing an autotools build then yes, adding the CMAKE_PREFIX_PATH will not resolve your problem - CMAKE is an alternative to autotools, not a helper tool or an addition. So if autotools fail for you, maybe just try the CMAKE way (look at README.cmake at the toplevel directory).

(29 Mar '16, 16:45) jmayer
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×53
×41
×25

question asked: 28 Mar '16, 11:19

question was seen: 2,057 times

last updated: 29 Mar '16, 16:45

p​o​w​e​r​e​d by O​S​Q​A