setenv-embedded.sh and GNUmakefile-cross

[crosswalking]

This is not a bug of crypto++ but rather a configuration issue in the files setenv-embedded.sh and GNUmakefile-cross. There is an ARM_EMBEDDED_SYSROOT setting which should not be used when cross-compiling on Linux (e.g. on desktop Ubuntu) for BeagleBone Black.

The issue is described at Linking error when compiling crypto++ for armhf, and I posted an answer on that webpage.

My solution was simply to remove the --sysroot option from line 68 in the file GNUmakefile-cross. My solution is not ideal, of course. It is just a shortcut.

[noloader]

I think this another distro problem, similar to g++-arm-linux-gnueabi cannot compile a C++ program with --sysroot. It might be a Ubuntu problem or a Debian problem if it is coming from upstream.

When cross-compiling, we expect the following (using ARMHF):

• SYSROOT is /usr/arm-linux-gnueabihf
• INCLUDEDIR is /usr/arm-linux-gnueabihf/include
• LIBDIR is /usr/arm-linux-gnueabihf/lib
• BINDIR is /usr/arm-linux-gnueabihf/bin

How LIBDIR morphed into into /usr/arm-linux-gnueabihf/usr/arm-linux-gnueabihf/lib/ (i.e., $SYSROOT/$SYSROOT/lib) is a mystery. But in all fairness, building GCC is not a trivial task.

You should probably file a bug report with Debian or Ubuntu (or whomever provides the toolchain).

[noloader]

I'm going to close this since it looks like a configuration problem with the distro toolchain.