Today's conclusion: most people on Twitter who think they know how the LGPL works actually don't (and won't read it and fix their misconceptions before randomly attempting to "correct" me).
Replying to @dvdgchrd
libgcc is a special case, deserving of a whole tweetstorm about how its licensing is a hack to deter proprietary GCC plug-ins. But the TL;DR is that libgcc is *GPL*, not *LGPL*, but then it comes with an exception that allows linking (including statically).
10:47 PM - 7 Aug 2018
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.