Thread: GPL violation?
View Single Post
Old 03-09-2008, 08:56 AM   #109
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,557
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
I'm curious as to what the practical difference is between statically and dynamically linking to a library in an embedded system such as the Gen3. Suppose you were to find a bug in the C runtime library - you couldn't do anything about it. Why does it therefore matter, from purely practical considerations, if you statically link the library?

I fully accept, by the way, that the LGPL says that you shouldn't. I'm asking here about the practical rather than the "legal" implications of doing so.
HarryT is offline   Reply With Quote