If you're using gcc and glibc in any halfway normal manner, and you want to distribute your binaries to customers, but not release your source code, that's ok. If you're doing anything strange, you might need to double-check. But in general, glibc is designed to avoid any worries about open source forcing you to release your source code in the great majority of cases. - Dan On Tue, Jul 7, 2020 at 6:46 PM JacobK622 via Gcc-help <gcc-help@xxxxxxxxxxx> wrote: > to: gcc help mailing-list > > I'm still a bit concerned about this. > > What are my obligations under the licenses? (or should I post that as a > new question?) > > Does anyone else have any thoughts on this? > > My email is JacobK622@xxxxxxxxxxxxxx feel free to email me at any > time,although I may not respond immediately. (usually within 24hrs.) > > From, Jacob K > > Sent with ProtonMail Secure Email.
