Re: [Discuss OpenCPI] Issue building OCPI components using new RCC platform based on N310 SDK

From: James Kulp <jek_at_parera.com>
Date: Mon, 15 Jul 19 08:52:01 -0400

Hi Robert,

Thanks for the report.
So the configure commands are the same in both cases, but are run in
different environments.
Perhaps you could dump the environment along with the set -x

Jim


On 7/12/19 5:53 PM, Munro, Robert M. wrote:
> OCPI Development Team,
>
> An Ettus N310 SDK environment is being integrated into the OCPI build environment to enable building software for the N310 target. The RCC platform has been set up and the core project appears to build successfully using 'ocpidev build project projects/core -rcc -rcc-platform ettus_n310_sdk'.
>
> When attempting to build the assets project the compiler throws an error when it doesn't find some libraries from the prerequisites. I have attempted using the command 'build/install-prerequisites.sh ettus_n310_sdk' to build and install all required prerequisites, but this fails in the configure operation of gmp. By navigating to the prerequisites-build/gmp/gmp-6.1.2/ocpi-build-ettus_n310_sdk/ and running the prescribed configure, make, make install commands the build completes without error. To see the difference between the two commands 'set +x .. set -x' was added around the configure command in build/prerequisites/gmp/install-gmp.sh .
>
> Failing configure command:
> ../configure --host=arm-oe-linux-gnueabi --prefix=/home/me/work/me/geontech/opencpi/prerequisites/gmp --exec-prefix=/home/me/work/me/geontech/opencpi/prerequisites/gmp/ettus_n310_sdk --enable-fat=yes --enable-cxx=yes --with-pic
>
> Failing configure output:
> checking whether /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/arm-oe-linux-gnueabi/arm-oe-linux-gnueabi-gcc is gcc... yes
> checking compiler /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/bin/arm-oe-linux-gnueabi/arm-oe-linux-gnueabi-gcc -O2 -pipe -g -feliminate-unused-debug-types ... no
> configure: error: could not find a working compiler, see config.log for details
>
> Working configure command:
> ../configure --host=arm-oe-linux-gnueabi --prefix=/home/me/work/me/geontech/opencpi/prerequisites/gmp --exec-prefix=/home/me/work/me/geontech/opencpi/prerequisites/gmp/ettus_n310_sdk --enable-fat=yes --enable-cxx=yes --with-pic
>
> Working configure output:
> checking whether arm-oe-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/usr/local/oecore-x86_64/sysroots/cortexa9hf-neon-oe-linux-gnueabi is gcc... yes
> checking compiler arm-oe-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/usr/local/oecore-x86_64/sysroots/cortexa9hf-neon-oe-linux-gnueabi -O2 -pipe -g -feliminate-unused-debug-types ... yes
>
> Since the install-prerequisites.sh script fails in gmp library, the liquid, lzma, and gtest libraries must be built and succeed using a similar manual approach. The assets project is then able to build several RCC elements until it reaches the ad9361_config_proxy.so where it is looking for the libad9361.a . After searching in similar places as the build steps for the other prerequisites (build/prerequisites/<library>) the appropriate instructions for manually building the ad9361 library are not able to be found. Where are the build steps described for this library?
>
> Likewise the build of the build/autotools/ products using this SDK requires manual configuration and is currently failing to complete.
>
> Is the use of a non-Xilinx SDK unsupported for the framework or are there more elements that can be supplied to the framework to support this use case? A copy of the RCC configuration file is attached for reference.
>
> Thank you,
> Robert Munro
>


Received on Mon Jul 15 2019 - 12:52:01 CDT