From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] llvm 3.7.1-1
Date: Mon, 22 Feb 2016 17:10:00 -0000 [thread overview]
Message-ID: <56CB40FA.7000306@cygwin.com> (raw)
In-Reply-To: <loom.20160222T102922-321@post.gmane.org>
On 2016-02-22 03:32, Tony Kelman wrote:
> Yaakov Selkowitz <yselkowitz <at> cygwin.com> writes:
>
>> This is an update to the latest upstream release. This release switches
>> to the CMake build, which results in many small shared libraries instead
>> of the single monolothic one from previous releases. Clang is also built
>> as a separate source package as a result.
>
> You're not supposed to use BUILD_SHARED_LIBS with LLVM's cmake build.
> They have a dedicated flag LLVM_BUILD_LLVM_DYLIB for this.
LLVM_BUILD_LLVM_DYLIB does not build correctly on Cygwin, where
BUILD_SHARED_LIBS does.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-02-22 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 8:36 Yaakov Selkowitz
2016-02-22 9:32 ` Tony Kelman
2016-02-22 9:36 ` Ismail Donmez
2016-02-22 17:10 ` Yaakov Selkowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56CB40FA.7000306@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).