What Compiler and options used for Raspian build

gmh

Hello, we're doing some experiments on a Raspberry Pi 4 (Raspbian GNU/Linux 10 (buster)) Using the ICE C++11 bindings with the g++ 8.3 compiler delivered with the OS. We're having occasional problems with ICE ( libzeroc-ice3.7:armhf package ). It behaves like an ABI issue, although I suppose it could be either general compiler options or the C++ ABI that changed at g++-7. Can you tell me what compiler version and compile options were used for this package?

xdm

Hi Greg,

We use the default OS compiler g++ 8.3, are you installing zeroc-ice packages from the debian repository or from a different source?
Do you have any more info about the failures?
You can try running the 3.7 test suite against the binary distribution to check if everything works

git clone [email protected]:zeroc-ice/ice.git
cd ice
make ICE_BIN_DIST=all CONFIGS=cpp11-shared V=1
ICE_BIN_DIST=all python allTests.py --config=cpp11-shared --all

We regularly run all tests on debian armhf and arm64 platforms and are not aware of any issues that affect the C++11 mapping, there is a known issue that affects the C++ 98 mapping but shouldn't matter for your case as you are using the C++11 mapping.
https://doc.zeroc.com/ice/3.7/release-notes/known-issues-and-platform-notes#id-.KnownIssuesandPlatformNotesv3.7-C++98Mappingand-stdoptiononLinuxARM

xdm

Hi Greg,

We use the default OS compiler g++ 8.3, are you installing zeroc-ice packages from the debian repository or from a different source?
Do you have any more info about the failures?
You can try running the 3.7 test suite against the binary distribution to check if everything works

git clone [email protected]:zeroc-ice/ice.git
cd ice
make ICE_BIN_DIST=all CONFIGS=cpp11-shared V=1
ICE_BIN_DIST=all python allTests.py --config=cpp11-shared --all

We regularly run all tests on debian armhf and arm64 platforms and are not aware of any issues that affect the C++11 mapping, there is a known issue that affects the C++ 98 mapping but shouldn't matter for your case as you are using the C++11 mapping.
https://doc.zeroc.com/ice/3.7/release-notes/known-issues-and-platform-notes#id-.KnownIssuesandPlatformNotesv3.7-C++98Mappingand-stdoptiononLinuxARM

gmh

Thanks. We'll keep investigating. When we build our application with -mcpu=cortex-a72, we have problems that would be explained by an ABI mismatch. Using -march=armv6+fp avoids the issue. I haven't seen anything to indicate that there are ABI differences by specifying a different cpu.