Linking issues between Linux and Windows built binaries about bleeding-edge-toolchain HOT 5 OPEN

Make sure it's the very same gcc revision for lto to work.
On Windows I suggest using WSL to build gcc.
Also I'm playing around with Github CI. You may try one of those builds: https://github.com/Trass3r/bleeding-edge-toolchain/actions
Or set it up in your fork: https://github.com/Trass3r/bleeding-edge-toolchain/blob/master/.github/workflows/CI.yml

from bleeding-edge-toolchain.

Make sure it's the very same gcc revision for lto to work.
On Windows I suggest using WSL to build gcc.
Also I'm playing around with Github CI. You may try one of those builds: https://github.com/Trass3r/bleeding-edge-toolchain/actions
Or set it up in your fork: https://github.com/Trass3r/bleeding-edge-toolchain/blob/master/.github/workflows/CI.yml

Thanks! That was quick :)

Good point, the Windows binaries we had appear to be few months old. I will check out your builds first.

from bleeding-edge-toolchain.

Note that I will rebase and squash all those test commits once I'm done.
Here's the last build that produced output: https://github.com/Trass3r/bleeding-edge-toolchain/runs/315655966

from bleeding-edge-toolchain.

Note that I will rebase and squash all those test commits once I'm done.
Here's the last build that produced output: https://github.com/Trass3r/bleeding-edge-toolchain/runs/315655966

Thanks. Last week I did grab the binaries from your earlier successful builds for testing with our codebase. Only then I noticed that you're using the gcc tip/master which currently appears to be version 10.0.0. I think officially we need to be using the 9.2.0 version since we're also making releases of our software. I forked from your master branch to try and switch to v 9.2.0 but I haven't yet had time to figure out what needs to be done for the github CI settings in order to successfully build the artifacts. Appears that some action settings are required for my account.

I did try using the 10.0.0 version in our builds but that yielded a different problem when compiling the app against the library. It says that a struct in Nordic's nRF5_SDK violates the C++ One Definition Rule. At quick glance there seems to be no redefinition. That problem does not exist for 9.2.0.

from bleeding-edge-toolchain.

You need to activate the actions first but then it should build.

you're using the gcc tip/master

Yes arm-gcc 8 and 9 had a few issues with objdump and LTO with debug info. Just change the versions at the top of the script from master to a release branch or tag.
Btw please refork, it's all rebased now.

If there's a bug please open a ticket in my repo or directly at the official bug tracker.

from bleeding-edge-toolchain.