From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Chances for llvm / clang update?
Date: Thu, 22 Apr 2021 09:08:56 -0600 [thread overview]
Message-ID: <0e94a48a-f169-5048-f840-85da0ef3f7ce@SystematicSw.ab.ca> (raw)
In-Reply-To: <002e01d73751$e5066840$af1338c0$@uni-bremen.de>
On 2021-04-22 02:31, Andreas Heckel via Cygwin wrote:
> Is there a chance for an "official" update of clang / llvm. Currently I
see v8 here on Cygwin while llvm is now at v12.
>
> I had tried to build v12 in Cygwin by simply running along the instructions on the llvm page. But I failed at a number of options / packages in the past and only got clang and a few tools like clang-format to run under Cygwin. I apologise, but I really have no clue about building anything properly for Cygwin (yet).
Install the latest llvm and clang *source* packages; and
binary packages: cygport, which pulls in all the usual tools, but also add
cmake, gnupg2, ninja, cygwin-devel, libc++-devel, libc++abi-devel,
libedit-devel, libffi-devel, libllvm-devel, libncurses-devel, libpolly-devel,
libunwind-devel, libxml2-devel, zlib-devel, python3-devel, python3-recommonmark,
python3-setuptools, and python3-sphinx;
change to the llvm source directory containing the llvm.cygport file;
edit llvm.cygport, and bump the major version 1 at a time, e.g. 9.0.1, 10.0.1
11.1.0, 12.0.0, including libllvm{9,10,11,12}, libpolly{9,10,11,12}, and save;
then run:
$ cygport llvm.cygport download all check
Pay attention to:
any warning or error messages about required packages missing, some of which may
be lib...-devel, which you have to install before retrying the build; and
build errors, which you have to resolve.
After a successful build, you will have binary and source tar and hint files
under llvm-#-1.*86*/dist/llvm/ which you may install on your system using:
$ tar -xv -C / -f llvm-#-1.*86*/dist/llvm/llvm-#-1.tar.xz
similarly for prerequisite dependencies and corequisite package tars under:
$ ls llvm-#-1.*86*/dist/llvm/{,*/}*-#-1.tar.xz
as packages are built under a virtual root directory, which you can see under
llvm-#-1.*86*/inst/...
Then repeat the process for clang using each recently built and installed llvm.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-04-22 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 8:31 Andreas Heckel
2021-04-22 9:47 ` Andrey Repin
2021-04-22 11:11 ` Marco Atzeri
2021-04-22 12:00 ` Andreas Heckel
2021-04-22 15:08 ` Brian Inglis [this message]
2021-04-22 15:45 ` Brian Inglis
2021-04-22 17:14 ` Andreas Heckel
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=0e94a48a-f169-5048-f840-85da0ef3f7ce@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).