Closed mhansen closed 7 months ago
Also possible I'm perhaps building against one Qt and trying to link against another version of Qt? Not sure.
I have not been successful in reproducing this issue. I was able to build and run traceshark with Big Sur and Qt 5.15.2.
I tried both installing Qt with brew and with macports. As far as I could tell, both worked. EDIT: As a side note, "make install" doesn't work for me either because it fails when trying to install the man page to some apparently incorrect path but I am able to build, link and run the traceshark binary.
Regarding the missing symbols, they are not used by traceshark directly but they are used indirectly through Qt's header files.
It looks to me as if the toolchain that compiled the traceshark object files has a disagreement with the toolchain that compiled the Qt library regarding various integer types.
For example, looking at the Qt sources, the prototype of one of the functions
is:
void QArrayData::deallocate(QArrayData *data, size_t objectSize, size_t alignment)
When I look at the preprocessed sources for my build of cpuselectmodel.o, I find these two lines:
typedef long unsigned int __darwin_size_t;
typedef __darwin_size_t size_t;
Apparently, some system header file used by my toolchain defines size_t to be long unsigned int
. Judging from the error message posted above, there size_t has apparently been defined as long long
.
So it seems likely that the traceshark object files have been compiled with a toolchain that is not fully compatible with the toolchain that Qt has been built with.
Another possibility is that some include path passed as an argument to the compiler is wrong but I consider this to be less likely.
Thanks for the debugging ideas and pointers. I'll give another go at debugging this.
There has been no activity on this for over two years. Also, nowadays, the recommended way to build for MacOS is to use brew to install Qt6 and that works for me. I believe that things has changed so much that the problems described here are probably moot.
If there are still issues with building for MacOS, please open a new issue.
Hi there, I'm not sure this is a huge priority (probably most users are on linux) but just reporting these issues compiling on macOS:
I'm not sure if this is a mismatch in Qt versions (I'm using 5.15 -- the version installed from
brew install qt@5
, the readme says 5.13. Or perhaps I'm just holding it totally wrong!