Errors on Building around Linux (armhf)

PX4 Autopilot
1 
sudo ./bin/px4 -s px4.config
[sudo] password for debian:
./bin/px4: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.34' not found (required by ./bin/px4)
./bin/px4: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.38' not found (required by ./bin/px4)
./bin/px4: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.29' not found (required by ./bin/px4)
./bin/px4: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.27' not found (required by ./bin/px4)
./bin/px4: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.38' not found (required by ./bin/px4)

These are my errors. I installed a toolchain, built the PX4 code with this command:

make ARCH=arm CROSS_COMPILE=MY_TOOLCHAIN_file/bin/arm-linux-gnueahihf- beaglebone_blue_default upload

The binary and files got installed but when I run:

sudo ./bin/px4 -s px4.config

I receive the first set of errors like my toolchain is old or too new. Is there a way on board the target device to handle changing the ldd version for using it with libc and libm on Debian/GNU Linux?

2

I have found that even with the CC= and/or CROSS_COMPILE= argument with the make command for the Makefile, I always get my installed GCC compiler installment used on the development desktop instead of the needed cross_compiler I call to use.

Is there a way to make sure I am using the called cross_compiler instead of the one that is native?

3

Okay…

I updated to the latest git clone repo, used the command make beaglebone_blue_default upload, and then received a new set of errors:

/ADS1115.h:149:21: error: enclosing class of constexpr non-static member function ‘unsigned int ADS1115::ch2u(ADS1115::Channel’ is not a literal type
  constexpr unsigned ch2u(Channel ch) { return (unsigned(ch) >> 4) & 0b11u; }
                     ^~~~
compilation terminated due to -Wfatal-errors.
[577/1090] Building CXX object src/drivers/gps/CMakeFiles/drivers__gps.dir/gps.cpp.o

It seems ch2u on the ADS1115.h file is returning an error.

I would also like to know if I could skip the librobotcontrol install on Debian/Ubuntu to make sure I can use the already-working install of librobotcontrol on the BBBlue?

If there are people using the BBBlue, please jump on in…

4

Finally. Got it. The errors I was seeing were due to the i686 toolchain (someone) installed in the directory files.

Blah…x86_64 is what was needed for the CC.

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.