<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font size="-1">Jukka's <a class="moz-txt-link-freetext" href="https://bugs.llvm.org/show_bug.cgi?id=46201">https://bugs.llvm.org/show_bug.cgi?id=46201</a>
      has</font><br>
    <blockquote>
      <pre class="bz_comment_text">Our release management at Unity are finding it difficult legal wise to redistribute LLVM,
as LLVM itself does not carry such a NOTICE file that would list the third party licenses of LLVM itself.
Such third party content is found for example at least in the following files

- llvm/lib/Support/COPYRIGHT.regex
- llvm/lib/Support/MD5.cpp
- llvm/lib/Support/xxhash.cpp
- llvm/utils/benchmark/LICENSE
- llvm/utils/unittest/googlemock/LICENSE.txt
- llvm/utils/unittest/googletest/LICENSE.TXT

(in addition to the main license in llvm/LICENSE.txt)
</pre>
    </blockquote>
    <p><font size="-1">The files under llvm/lib/Support may need a
        LICENSE.txt. Each of the three files has a different license.
        The apparent remaining issue is how to have a LICENSE.txt in
        this case and if there are similar cases not accounted for.<br>
      </font></p>
    <p><font size="-1">Neil Nelson</font></p>
    <div class="moz-cite-prefix"><font size="-1">On 6/5/20 10:58 AM,
        Chris Lattner via llvm-dev wrote:</font><br>
    </div>
    <blockquote type="cite"
      cite="mid:A1C9F614-44CF-4A32-A2DE-A2D9D0E675D4@nondot.org">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      Hi Jukka,
      <div class=""><br class="">
      </div>
      <div class="">We discussed this with the LLVM Foundation board.
         While we think there is high utility to providing such a
        NOTICES file, we don’t know of a way to keep it up to date, and
        don’t want to be providing incorrect information for such an
        important topic.</div>
      <div class=""><br class="">
      </div>
      <div class="">That said, the llvm/LICENSE.TXT checked into the
        code has this information about how to identify third party
        licenses in the code base.  I hope this is enough to help with
        your analysis.</div>
      <div class=""><br class="">
      </div>
      <div class="">
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">==============================================================================</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">Software
            from third parties included in the LLVM Project:</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">==============================================================================</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">The
            LLVM Project contains third party software which is under
            different license</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">terms.
            All such code will be identified clearly using at least one
            of two</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">mechanisms:</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">1)
            It will be in a separate directory tree with its own
            `LICENSE.txt` or</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">  
            `LICENSE` file at the top containing the specific license
            and restrictions</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">  
            which apply to that software, or</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">2)
            It will contain specific license and restriction terms at
            the top of every</span></div>
        <div style="margin: 0px; font-stretch: normal; font-size: 11px;
          line-height: normal; font-family: Menlo;" class=""><span
            style="font-variant-ligatures: no-common-ligatures" class="">  
            file.</span></div>
      </div>
      <div class=""><br class="">
      </div>
      <div class="">Thanks!</div>
      <div class=""><br class="">
      </div>
      <div class="">-Chris</div>
      <div class=""><br class="">
      </div>
      <div class=""><br class="">
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">On Jun 4, 2020, at 10:51 PM, Jukka Jylänki via
              llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org"
                class="" moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div class="">Hello all,<br class="">
                <br class="">
                I was asked to bring attention to this LLVM ticket to
                the mailing list:<br class="">
                <br class="">
                <a href="https://bugs.llvm.org/show_bug.cgi?id=46201"
                  class="" moz-do-not-send="true">https://bugs.llvm.org/show_bug.cgi?id=46201</a>
                - Missing LLVM NOTICE file<br class="">
                is making redistributing LLVM difficult.<br class="">
                <br class="">
                It was recently noted by our legal review in release
                management that<br class="">
                LLVM third-party licenses are scattered over different
                files, which<br class="">
                complicates faithful license-preserving redistribution
                of LLVM to our<br class="">
                users. Having a grouped license declaration of would
                make building<br class="">
                redistributables easier.<br class="">
                <br class="">
                Best,<br class="">
                Jukka<br class="">
                _______________________________________________<br
                  class="">
                LLVM Developers mailing list<br class="">
                <a href="mailto:llvm-dev@lists.llvm.org" class=""
                  moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br
                  class="">
                <a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br
                  class="">
              </div>
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
    </blockquote>
  </body>
</html>