ERROR: ld.so: object '/home/jazocar/Descargas/build-wrapper-linux-x86/libinterceptor-${PLATFORM}.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
build-wrapper: execvp: No such file or directory
This forum is in English language, we don’t understand Spanish.
From the error message that you display, it looks like there is a problem with your installation of the build wrapper tool. Did you just unzip the full downloaded package into one folder, and tried to execute it from there?
then I went to the folder of the “C” files and run build-wrapper-linux-x86-64 --out-dir bw_output xcodebuild clean build and I get the following error
jazocar@juliopc:~/Descargas/sonar-scanner-3.2.0.1227-linux/bin/cred2$ build-wrapper-linux-x86-64 --out-dir bw_output xcodebuild clean build
ERROR: ld.so: object '/home/jazocar/Descargas/build-wrapper-linux-x86/libinterceptor-${PLATFORM}.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
build-wrapper: execvp: No such file or directory
As far as I know, it’s not possible to run xcodebuildr from a linux machine, you have to be on a Mac. So either you run the build-wrapper on a Mac box, or, if the code is portable, you may run it from Linux, but you will need a command-line that does not involve xcodebuild.
By the way, it you try to run build-wrapper-linux-x86-64 --out-dir bw_output {something} and it does not work, the first step would be to check that running {something} independently works.
And search if the resulting output contains libinterceptor-haswell.so . If so, you are in the same situation, and you can work around it by using the same way that was proposed there:
If not, we don’t yet know what happens, and we might be interested in getting the files generated by this strace command to look at them more deeply, as well as the logs from the build wrapper (they will be in the bw_output folder).
I do not compile them, these files are from a client who wants to evaluate if they integrate sonarcube, they have many c files, I would say 500,000 rows and they need to test with this file, but in the test they do, it only throws duplicate code in sonarqube , or test on your pc quisaz leaves only duplicate code as a result in sonarqube Thank you
The first step to analyze C code is first to build it (just to make sure that it works), then build it again, but from the build wrapper to get some required and important information about what happens during the build, then only run the analysis itself.
If you can’t build the code, you won’t be able to analyze it.
Sorry, but I don’t understand what you ask. To analyze C code, you first have to build it. If you don’t know how to build it, you should ask assistance to people to first wrote it.