From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Doxygen 1.8.16
Date: Fri, 30 Aug 2019 17:28:00 -0000 [thread overview]
Message-ID: <fee6b475a6d01e46091f8688e437066d83df39e8.camel@cygwin.com> (raw)
In-Reply-To: <c7b140bd-a8c9-30a3-44f6-e3cf8ca5f371@cornell.edu>
On Fri, 2019-08-30 at 12:42 +0000, Ken Brown wrote:
> On 8/29/2019 11:34 AM, Yaakov Selkowitz wrote:
> > On Thu, 2019-08-29 at 14:25 +0000, Ken Brown wrote:
> > > On 8/29/2019 8:51 AM, Kptain wrote:
> > > > Is it possible to make available release 1.8.16 of Doxygen as lot of fixes
> > > > have been provided?
> > >
> > > Yes, I'll do that within the next few days.
> >
> > When you do, make sure you update your installation first as LLVM/Clang
> > was just updated, and doxygen is the last package using the old
> > version.
>
> The doxygen build with the latest LLVM fails as follows:
>
> CMake Error at CMakeLists.txt:44 (find_package):
> Found package configuration file:
>
> /usr/lib/cmake/llvm/LLVMConfig.cmake
>
> but it set LLVM_FOUND to FALSE so package "LLVM" is considered to be NOT
> FOUND. Reason given by package:
>
> The following imported targets are referenced, but are missing: LLVMSupport
> LLVMCore LLVMScalarOpts LLVMInstCombine LLVMTransformUtils LLVMAnalysis
> LLVMipo LLVMMC LLVMPasses LLVMLinker LLVMIRReader LLVMBitReader
> LLVMMCParser LLVMObject LLVMProfileData LLVMTarget LLVMVectorize
>
> I don't know much about CMake or LLVM. Any idea what's going on?
This may be a symptom of the switch from a single to multiple shared
libraries. In /usr/lib/cmake/llvm/LLVMConfig.cmake, could you try
moving the line which imports LLVMStaticExports up a few lines, just
above the import of LLVMExports?
--
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
next prev parent reply other threads:[~2019-08-30 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 14:25 Kptain
2019-08-29 15:05 ` Ken Brown
2019-08-29 16:37 ` Yaakov Selkowitz
2019-08-29 20:24 ` Ken Brown
2019-08-30 9:54 ` Kptain
2019-08-30 12:57 ` Ken Brown
2019-08-30 17:28 ` Yaakov Selkowitz [this message]
2019-08-30 18:20 ` Ken Brown
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=fee6b475a6d01e46091f8688e437066d83df39e8.camel@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).