[cfe-dev] Dynamic linked (.so) files for clang?
davejohansen at gmail.com
Fri Nov 28 14:07:42 PST 2014
I'm working on packaging include-what-you-use (
https://code.google.com/p/include-what-you-use/ ) for Fedora/RHEL (
https://bugzilla.redhat.com/show_bug.cgi?id=1091659 ) and the packaging
guidelines strongly discourage linking against static libraries (
). I'm putting in an exception request for the time being, but are there
any plans in the long term to build the dynamic libraries for clang?
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>
>> 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 (
>> 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.
>> cfe-dev mailing list
>> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev