BoomerangDecompiler / boomerang

Boomerang Decompiler - Fighting the code-rot :)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Build failing when building tests

Fighter19 opened this issue · comments

[ 65%] Linking CXX executable ../../../out/TypeTest
CMakeFiles/TypeTest.dir/TypeTest.cpp.o: In function `TypeTest::testDataInterval()':
TypeTest.cpp:(.text+0x1ede): undefined reference to `bool QTest::qCompare<bool, int>(bool const&, int const&, char const*, char const*, char const*, int)'
TypeTest.cpp:(.text+0x1f68): undefined reference to `bool QTest::qCompare<bool, int>(bool const&, int const&, char const*, char const*, char const*, int)'
collect2: Error: ld returned 1
commented

I need to do a pull-request again for my fork, should be fixed if I start a pull request with:
reductor@7a3ae1e

@Fighter19 Which compiler ? Which Qt ?

@nemerle, it's the linker.
On May 19, 2016 7:23 AM, "Artur K." notifications@github.com wrote:

@Fighter19 https://github.com/Fighter19 Which compiler ? Which Qt ?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#61 (comment)

@hakusdream The linker is reporting the error, but the missing reference might be caused by bad compiler-qt version: Qt compiled for vs2013 used with vs2015

Mismatched header/binary.

commented

Probably different versions of Qt, one which requires consistent types, the other did not.

It's just a template function that ensures types don't match for comparison and there is no implicit conversions happening, changing them to failing locations from ints to bools fixes the issue. (See earlier referenced commit)

@reductor See #62.

Rebase your commits, also.

Actually this problem occured on ArchLinux with the current up-to-date libraries.

[xxxxxx@XXXX lib]$ qmake -version
QMake version 3.0
Using Qt version 5.6.0 in /usr/lib

Disabling the test, I was able to compile the rest. Also some other tests successfully compile, but I didn't test further.

I'll try on Ubuntu though Travis-CI.
On May 19, 2016 10:33 AM, "Fighter19" notifications@github.com wrote:

Actually this problem occured on ArchLinux with the current up-to-date
libraries.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#61 (comment)