grsecurity's RAP includes a GPLv2-only compiler plugin (uses headers) for GPLv3-only GCC. QED.
-
-
https://grsecurity.net/rap_faq.php . Last section. QED my ass.
1 reply 0 retweets 0 likes -
Yes, that is
@paxteam's hilarious licensing hack. It's wrong. The libgcc exception has *nothing* to do with GCC's license.1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
GCC is GPLv3, period, and the plugin system uses direct calls, and thus plugins are derived works, and thus they have to be GPLv3.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
What they claim *only* works if you use a GPLv3 shim to serialize compilation data into a non-linking format then operate on that.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
They do NOT do that, they wrote a simple plugin, which has to be GPLv3 because it DIRECTLY links into and calls GPLv3'd GCC.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
Nevermind the fact that there are many Linux arch ports that DO link libgcc, so they're wrong (or lying) about that too.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @lazytyped and
"config PAX_RAP depends on X86_64 && GCC_PLUGINS" your point being?
2 replies 0 retweets 0 likes -
Replying to @_pablosole_ @lazytyped and
Your point being? I already told you my point: PAX_RAP is GPLv2 licensed and *links against* GPLv3'd GCC. That's a violation.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @_pablosole_ and
Sure, RAP *today* may only work for x86. They conveniently forget to mention that it won't be portable to other arches thanks to this.
1 reply 0 retweets 0 likes
And that's ignoring the elephant in the room of the blatant plugin licensing problem, which is much bigger than the libgcc issue.
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.