I'm currently porting over my work I've done with v1.5.1 to v1.6.0 and I have run into an issue when running the following command: $ ./scripts/install-opencpi.sh xilinx17_4 I have created a xilinx17_4 RCC that works well under v1.5.1. Under v1.6.0, it seems there is an issue with the install-gpsd.sh script. I get this at the time of the error: scons: done building targets. arm-linux-gnueabi-ar: libgpsmm.o: No such file or directory ====== Build/install of gpsd prerequisite failed. When I try to find the file, I get two locations: ./prerequisites-build/gpsd/gpsd/ocpi-build-xilinx17_4/ocpi-build-ubuntu16/libgpsmm.o ./prerequisites-build/gpsd/gpsd/ocpi-build-ubuntu16/libgpsmm.o So it seems like maybe the command to tell scons where to put the results or where to build in general is getting a little screwed up. It seems this script is new for v1.6.0, so I am curious how others got past this issue when building? Am I doing something wrong? Any pointers would be appreciated. Thanks, Brian

I've solved my own issue. Sorry for the chatter. On Wed, Mar 4, 2020 at 7:57 PM Brian Padalino <bpadalino@gmail.com> wrote: > I'm currently porting over my work I've done with v1.5.1 to v1.6.0 and I > have run into an issue when running the following command: > > $ ./scripts/install-opencpi.sh xilinx17_4 > > I have created a xilinx17_4 RCC that works well under v1.5.1. Under > v1.6.0, it seems there is an issue with the install-gpsd.sh script. I get > this at the time of the error: > > scons: done building targets. > arm-linux-gnueabi-ar: libgpsmm.o: No such file or directory > ====== Build/install of gpsd prerequisite failed. > > When I try to find the file, I get two locations: > > > ./prerequisites-build/gpsd/gpsd/ocpi-build-xilinx17_4/ocpi-build-ubuntu16/libgpsmm.o > ./prerequisites-build/gpsd/gpsd/ocpi-build-ubuntu16/libgpsmm.o > The second location was because the 'source' directory was copied over to the 'build' directory, which was built previously for my host RCC. So it had the same artifacts from beforehand due to the previous build. > > So it seems like maybe the command to tell scons where to put the results > or where to build in general is getting a little screwed up. It seems this > script is new for v1.6.0, so I am curious how others got past this issue > when building? Am I doing something wrong? > The issue was that my cross compiler did not have a tool called `c++`, but only `g++`. I could either make a symbolic link in my path from {cross}-c++ -> {cross}->g++, or add a patch to be applied to make it say g++ instead of c++ for the CXX tool in the SConstruct file. Essentially, without a working C++ compiler, libgpsmm.o would not get built and things would fail. Again, sorry for the chatter. Brian >