[llvm-dev] [cfe-dev] clang in official apt repo built without z3 support

Mikhail Ramalho via llvm-dev llvm-dev at lists.llvm.org
Tue Feb 12 12:16:29 PST 2019


On Tue, 12 Feb 2019, 15:57 Paulo Matos <pmatos at linki.tools wrote:

>
>
> On 12/02/2019 19:49, Mikhail Ramalho wrote:
> >
> >
> > On Tue, 12 Feb 2019, 14:32 Paulo Matos <pmatos at linki.tools wrote:
> >
> >
> >
> >     On 12 February 2019 18:59:21 CET, Mikhail Ramalho
> >     <mikhail.ramalho at gmail.com <mailto:mikhail.ramalho at gmail.com>>
> wrote:
> >     >I _think_ there is a problem with the license as well: Z3 is MIT, so
> >     >clang
> >     >would have to be released with Z3's license.
> >
> >     I don't think that's a problem. You are not releasing z3 with clang.
> >     This is an apt repo.
> >
> >
> > Well, I'm not an expert, but building clang linked with z3 and offering
> > it online for people to download seems a lot like a release.
> >
> > I don't it matters if it's a tar.gz or an apt repo.
> >
>
> Ah, ok you're linking clang with libz3 or so? ...
>
> Still... I am definitely not an expert in licensing but after a quick
> lookup on Google, I would say that Apache2 and MIT would not cause a
> problem. Anyway, don't quote me on that.
>

AFAIK, the only requirement is to ship Z3's license along with the clang.

I heard that there are other projects under the llvm umbrella with the same
issue (linking against MIT/apache2 libraries) and that they're not released
with llvm because this requirement.


>
> --
> Paulo Matos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190212/0a3c371f/attachment.html>


More information about the llvm-dev mailing list