Hi,
I have came back to getting a Linaro Jenkins local build working by pairing down the IFC6410 script.
I have came to a point where the cross platform build tools are not working !
It does not look like the script installs them properly and I am confused as to wether the script actually installs them or whether it erroneously relies on them being present on the build machine ?
I have attached my paired down .yaml script and the output build log.
Either I am doing something wrong or the normal Qualcomms script does actually load the build tools. So either theres a bug to be fixed or I need to know how to install the build tools or both !
Many thanks in advance,
Aaron
I am getting the following errors :-
~~~~~
20:24:02 ++ sh /var/lib/jenkins/jobs/lt-qcom-debian-images/workspace/scripts/gcc-version.sh -p arm-linux-gnueabihf-gcc 20:24:02 /var/lib/jenkins/jobs/lt-qcom-debian-images/workspace/scripts/gcc-version.sh: 25: /var/lib/jenkins/jobs/lt-qcom-debian-images/workspace/scripts/gcc-version.sh: arm-linux-gnueabihf-gcc: not found 20:24:02 /var/lib/jenkins/jobs/lt-qcom-debian-images/workspace/scripts/gcc-version.sh: 26: /var/lib/jenkins/jobs/lt-qcom-debian-images/workspace/scripts/gcc-version.sh: arm-linux-gnueabihf-gcc: not found 20:24:02 /var/lib/jenkins/jobs/lt-qcom-debian-images/workspace/scripts/gcc-version.sh: 28: /var/lib/jenkins/jobs/lt-qcom-debian-images/workspace/scripts/gcc-version.sh: arm-linux-gnueabihf-gcc: not found
....
18:29:07 ++ make mrproper 18:29:07 make: arm-linux-gnueabihf-gcc: Command not found 18:29:07 cat: write error: Broken pipe 18:29:10 ./scripts/gcc-version.sh: line 25: /var/lib/jenkins/srv/toolchain/arm-tc-14.04/bin/arm-linux-gnueabihf-gcc: No such file or directory 18:29:10 ./scripts/gcc-version.sh: line 26: /var/lib/jenkins/srv/toolchain/arm-tc-14.04/bin/arm-linux-gnueabihf-gcc: No such file or directory 18:29:10 ./scripts/gcc-version.sh: line 25: /var/lib/jenkins/srv/toolchain/arm-tc-14.04/bin/arm-linux-gnueabihf-gcc: No such file or directory 18:29:10 ./scripts/gcc-version.sh: line 26: /var/lib/jenkins/srv/toolchain/arm-tc-14.04/bin/arm-linux-gnueabihf-gcc: No such file or directory
~~~~~
/var/lib/jenkins/srv/toolchain/arm-tc-14.04/bin/arm-linux-gnueabihf-gcc is a link to arm-linux-gnueabihf-gcc-4.8.3 which exists, but when ran produces the "No such file or directory" message.
Very confused !
On 5 February 2016 at 14:36, Aaron Gray aaronngray.lists@gmail.com wrote:
Hi,
I have came back to getting a Linaro Jenkins local build working by pairing down the IFC6410 script.
I have came to a point where the cross platform build tools are not working !
It does not look like the script installs them properly and I am confused as to wether the script actually installs them or whether it erroneously relies on them being present on the build machine ?
I have attached my paired down .yaml script and the output build log.
Either I am doing something wrong or the normal Qualcomms script does actually load the build tools. So either theres a bug to be fixed or I need to know how to install the build tools or both !
Many thanks in advance,
Aaron
On Fri, Feb 5, 2016 at 12:30 PM, Aaron Gray aaronngray.lists@gmail.com wrote:
/var/lib/jenkins/srv/toolchain/arm-tc-14.04/bin/arm-linux-gnueabihf-gcc is a link to arm-linux-gnueabihf-gcc-4.8.3 which exists, but when ran produces the "No such file or directory" message.
You can get this message when the interpreter for a program is missing. For an elf binary, the interpreter would be the dynamic linker, which is probably something like /lib/ld-linux-armhf.so.3 for a armhf native binary. However, different operating systems may have different names for the file, or may place it in different directories. So you may have a binary that will run on some linux systems, but not yours. Or maybe there is some 32-bit/64-bit confusion here, and you need to install some packages to support the other bit size to make this binary work. You should try running ldd on the binary, and verify that the dynamic linker can be found.
Jim
Turned out to be several libraries lib32stdc++6, libc6-i386, and lib32z1, and possibly a path problem, will have to check this.
On 5 February 2016 at 20:58, Jim Wilson jim.wilson@linaro.org wrote:
On Fri, Feb 5, 2016 at 12:30 PM, Aaron Gray aaronngray.lists@gmail.com wrote:
/var/lib/jenkins/srv/toolchain/arm-tc-14.04/bin/arm-linux-gnueabihf-gcc is a link to arm-linux-gnueabihf-gcc-4.8.3 which exists, but when ran produces the "No such file or directory" message.
You can get this message when the interpreter for a program is missing. For an elf binary, the interpreter would be the dynamic linker, which is probably something like /lib/ld-linux-armhf.so.3 for a armhf native binary. However, different operating systems may have different names for the file, or may place it in different directories. So you may have a binary that will run on some linux systems, but not yours. Or maybe there is some 32-bit/64-bit confusion here, and you need to install some packages to support the other bit size to make this binary work. You should try running ldd on the binary, and verify that the dynamic linker can be found.
Jim
-
Aaron Gray -
Jim Wilson