Closed eacmen closed 6 years ago
Hi, just double-checked the build_release script against master, and it built successfully.
Can you confirm the OS and version of GCC you're using?
I am using gcc-arm-none-eabi-4_9-2014q4
download linked off the main page:
$ arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.9.3 20141119 (release) [ARM/embedded-4_9-branch revision 218278]
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Host native compiler:
$ gcc --version
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I assumed the whole build was using the arm compiler. but it looks like your test harness is building the code natively? This is likely the issue.
I am running debian 9. I tried configuring my system gcc to be 6.0, 4.9 and 4.6 and they all error'd out in different ways. What gcc version is required for the native build?
Hi,
this is what gcc --version reports currenty:
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
Closing due to inactivity. Peter, if you want to just submit the PR, we can take a look at it. Thanks!
I am trying to test/submit a PR and following the contributing guide
do_release.sh
must pass. However this script does not pass even on clean release tags I have checked out. It always errors on-Werror=misleading-indentation
, which I assume is trying to enforce a coding standard? Here is the output: Relavant info:When I build just the mk3 firmware I am interested in it builds just fine.