lkml.org 
[lkml]   [2000]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    David Woodhouse wrote:
    > But how much work would it require to do so? If your theoretical vendor of
    > closed-source compiler backends were to believe that a shared lib of the
    > GCC frontend would be legal, surely they'd just make it shared themselves,
    > then use it as such? It's hardly a effective preventative measure.

    Yes, there is nothing to prevent a vendor doing that _if_ they take care
    to ensure their proprietary code doesn't include inline functions /
    large macros etc. from the GCC header files.

    A clean interface to the shared library, where the interface is written
    by that vendor would do it. The interface code would have to be
    released under a GPL compatible license, that also permits the vendor to
    make use of it. E.g. LGPL would do for the interface header files, as
    would many other licenses.

    Such a thing won't be accepted into the main GCC distribution though.

    It's probably easier to use a pipe anyway.

    -- Jamie
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 12:38    [W:4.307 / U:0.064 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site