Label: compile

Content with label compile in Knowledge Base
Related Labels: manifest, dll, german, status_127, gcc, dependency, configure, java, install, qt, symbol, specified_procedure, mac, error, windows, embedded, linux, diagnostic, specified_module, more »

Page: Configure run fails with error about C++ not being found
Symptom When running the configure script ./configure withqmake=<pathtoqmake>/qmake enableqmakeconfig .... to build Squish from sources the script aborts with either of these two errors Checking for C compiler ......... Can't find any C compiler Check config.log for details ...
Other labels: error, configure
Page: Cross-compilation fails with "g++ not found"
Symptom A crosscompilation build from sources runs into the problem during the configure run with the following error: Using Source directory: /home/user/squish6.0.0qtembeddedsrc Using Build directory: /home/user/Squish/squish6.0.0qtembeddedsrc Using g compiler for bootstrapping Compiling configure and build ...
Other labels: error, status_127
Page: Cross-compiler with --sys-root switch "not found"
Symptom A crosscompilation build from sources runs fails when the {{XCXX}} crosscompiler variable contains a sysroot argument: $ ./build sh: 1: aarch64gnulinuxg sysroot=/home/user/sdk/sysroots/aarch64gnulinux: not found Aborting build. Last command exited with status ...
Other labels: error, status_127
Page: Error "Failed to build a simple Qt application"
Symptom During a build from sources the {{configure}} script fails with: Failed to build a simple Qt application, building Squish is very likely to fail too. This error message is emitted if a sanity check signals that the detected (or specified) build configuration is invalid ...
Other labels: error
Page: Error message "libts-1.0.so.0 not found"
Symptom When compiling for an embedded system that has Qt configured to use the libts touch screen library customers have reported linking errors like the one below: /home/user/squish/armfsllinuxgnueabi/bin/../lib/gcc/armfsllinux ...
Other labels: error, embedded
Page: Error message "Loading Qt Wrapper failed", "The specified procedure could not be found." (Qt)
Table of Contents Symptoms The Qt 4 binary edition is linked against a Qt 4 binary edition from The Qt Company, or against a Qt 4 source build with the standard Qt configuration. If a Qt 4 library is used in which certain ...
Other labels: diagnostic, specified_procedure, dll, error, procedure, windows, german
Page: Error message "Resolving symbol '' failed"
Symptom Customers have reported the following error to show up in the squishserver log when executing a test with a selfbuild installation: Preload (.....): Resolving symbol '' failed: ..../libQtGui.so.4: undefined symbol: Consequently, hooking into the application and record & replay of scripts will fail. Possible ...
Other labels: error, symbol
Page: Error message "Syntax error, word unexpected (expecting ")")"
Symptom A crosscompilation build from sources runs into the problem of internal tools like {{squishidl}} or {{conf}} failing with an "Syntax error": Compiling configure and build ... /home/user/squishembedded/conf: 1: Syntax error: word unexpected (expecting ")") Possible ...
Other labels: error
Page: Error Message "undefined symbol __sync_fetch_and_add_4"
Symptom When trying to test an application with a build from sources the startup via squishserver fails with the following error on the ARM platform: /path/to/aut: symbol lookup error: /path/to/squish/lib/libsquishqtpre.so: undefined symbol: syncfetchandadd4 Possible ...
Other labels: error
Page: How to build a 32-bit Squish on a 64-bit Linux System (Qt)
build a 32bit Qt using {{gcc}} on a 64bit Linux system, it is necessary to configure Qt with the argument: {{platform linuxg32}} Normally, Squish will build as a 64bit application on a 64bit system, so to force Squish to build as a 32bit application to be compatible with your 32bit ...
Other labels: gcc, linux, 32bit, 64bit, flags, qt