[cfe-dev] Dynamic linked (.so) files for clang?

[Dave Johansen]

Ok, that's unfortunate but explains it.
Thanks,
Dave

On Mon, Nov 24, 2014 at 10:48 AM, Reid Kleckner <rnk at google.com> wrote:

> The clang executable has always been linked statically, and does not
> actually depend on libclang.so. There isn't support yet for linking the
> bulk of Clang's internal libraries into shared libraries. For now, they are
> all static.
>
> On Mon, Nov 24, 2014 at 8:39 AM, Dave Johansen <davejohansen at gmail.com>
> wrote:
>
>> I'm the packager for llvm for the EPEL and it appears that all of the .so
>> files aren't being generated for clang. For example, libclang.so is being
>> generated (
>> http://pkgs.org/centos-6/epel-x86_64/clang-3.4.2-1.el6.x86_64.rpm.html )
>> but several of the symbols are only available in statically linked (.a)
>> files (
>> http://pkgs.org/centos-6/epel-x86_64/llvm-static-3.4.2-1.el6.x86_64.rpm.html
>> ).
>>
>> Is there something I can do to get all of the .so files to be generated?
>>
>> If it helps, the .spec file that I'm using can be found at
>> http://pkgs.fedoraproject.org/cgit/llvm.git/tree/llvm.spec?h=el6 and the
>> configure command starts on line 320.
>>
>> Thanks,
>> Dave
>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20141124/b3014c9d/attachment.html>