We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I have a confusion regarding GNU compiler licesnce. I gone through GNU ARM Embedded Toolchain license and noticed it has built with "newlib" C standard library instead of glibc to avoid licensing issue.
But still i want to clarify my confusion for below questions
1. Let's say i have a permissive BSD licensed opensource code, which i want to compile and put the outcome binary into commerical product. For this can i use GNU ARM Embedded Toolchain for compilation?
- Compiler adds some symbols sometimes into binary, example unwind related symbol, does it have any licensing issue?
- Is is statically linking is okay? because binary might need library symbols from toolchain.
Please some clarify.
Hello Manohara,
have you found the answer so far?
Currently I face the same problem. I wold like to use GNU ARM Embedded Toolchain to compile commercial product (sell the programmed device, no opensource). I thing compiling is ok, but there is problem with libraries. There is an exception from GPL for runtime libraries, which i guess is libgcc. The part about runtime library is not much clear to me. Is libc a runtime library or not? What about libm, libstdc++ and others?