C++ bitbucket-pipeline doesn't recognize pre-built library file

Question

I have set up the bitbucket-pipeline for our project, with custom GCC installation on docker space. ,we could build bootloader but when it comes to build the application code all our c source code mentioned in cmake were built, but bitbucket doesn't link the pre-built library files mentioned in cmake though the files located in the folder. Bitbucket throws no such file or folder. bitbucket-pipeline.yml file: image: gcc:10.2 pipelines: pull-requests: '**': - step: name: build script: - apt-get update - apt-get install -y cmake - chmod +x install_crosstoolchain.sh - ./install_crosstoolchain.sh - make snippet of cmake file where our .a file is located on main directory DXXXLIB = DXXXXX/XXX.a bitbucket error: arm-none-eabi-gcc: DXXXXX/XXX.a: No such file or directory184 make[1]: *** [Makefile.general:1237: Application] Error 1Please guide us to fix this.It was the same issue with other library files but with building source code for it generated new library for it and problem vanished. This particular library file we can't generate it and its a from third party.

Norbert Csupka · Answer

Looking at the error, I'm wondering if this is caused by the architecture What I can see is that you're trying to compile for arm arm-none-eabi-gcc: DXXXXX/XXX.a: No such file or directory But Pipelines is running on amd64 infrastructure. Do you know if you can compile this code in an amd64 arch? Also I would like to ask if you could try to reproduce this build in a Docker container? Do you have the same behavior? Steps to do it isgit clone https://@bitbucket.org/xxxxx/xxxxx.web cd xxxxxxx git checkout docker run -it --volume=:/xxxxxx --workdir="/xxxxxx" --memory=8g --memory-swap=8g --memory-swappiness=0 --entrypoint=/bin/bash gcc:10.2 ####once you're in the conatiner - apt-get update - apt-get install -y cmake - chmod +x install_crosstoolchain.sh - ./install_crosstoolchain.sh - make

Avanthi Busireddy · Answer

@Norbert Csupka Norbert Do you have any solution for this?

Avanthi Busireddy · Answer

I tried with the absolute path /opt/atlassian/pipelines/agent/build but still it didn't work.

The problem here is with linking the library files generated by another compiler I guess. I had the same issue with another library file, but since we have source code for it I made it compiled here within bitbucket and the linker could locate the generated file.