Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test all compilers in Travis which are allowed in the makefile #2294

Closed
LorenzMeier opened this issue Jun 6, 2015 · 7 comments
Closed

Test all compilers in Travis which are allowed in the makefile #2294

LorenzMeier opened this issue Jun 6, 2015 · 7 comments
Assignees

Comments

@LorenzMeier
Copy link
Member

Currently we're not testing all supported compilers in Travis. Current issue to be addressed:

PX4/Firmware/src/lib/uavcan/libuavcan/include/uavcan/marshal/array.hpp:516:13: error: comparison is always false due to limited range of data type [-Werror=type-limits]
@LorenzMeier LorenzMeier added this to the 2nd Beta release milestone Jun 6, 2015
@LorenzMeier LorenzMeier self-assigned this Jun 6, 2015
@LorenzMeier
Copy link
Member Author

@pavel-kirienko @davids5 It would be great if you could have a look at the error message above.

@pavel-kirienko
Copy link
Member

What compiler produced this error?

@kd0aij
Copy link
Contributor

kd0aij commented Jun 6, 2015

arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.7.4 20140401 (release) [ARM/embedded-4_7-branch revision 209195]

@pavel-kirienko
Copy link
Member

Fixed in master.

@dagar
Copy link
Member

dagar commented Feb 28, 2016

Do you want to support gcc 4.7-4.9? We could easily split this into 3 travis-ci linux builds that run in parallel, but we'd need to decide which one deploys to s3 and github releases.

@LorenzMeier
Copy link
Member Author

4.8 and 4.9 would be good.

@LorenzMeier
Copy link
Member Author

Doing that today, thanks @dagar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants