public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "徐持恒 Xu Chiheng" <chiheng.xu@gmail.com>
To: ASSI <Stromeko@nexgo.de>
Cc: cygwin-apps@cygwin.com
Subject: Re: [ITA] llvm
Date: Tue, 16 Jan 2024 13:19:17 +0800	[thread overview]
Message-ID: <CAPOVtOubMeUkub2V40GFJq0ad5Nqp5-s8cAC6aTF79p+V-=wkg@mail.gmail.com> (raw)
In-Reply-To: <875xzvljus.fsf@Gerda.invalid>

On Mon, Jan 15, 2024 at 4:51 AM ASSI via Cygwin-apps
<cygwin-apps@cygwin.com> wrote:
>
> LLVM 16 does indeed build (didn't look at the other two versions), but
> the cygport misses all the work to actually produce packaging that can
> be used to upgrade from the existing Cygwin version.  Source file is he
> whole project instead of just LLVM + Polly and the build also enables
> clang (which should be in a separate package).  Generator has been
> changed from Ninja to Make (and switching back to Ninja makes the
> install step fail because that target wasn't made available).  Multiple
> build options have been changed from what they were in Cygwin, I have
> not had time to investigate what that actually means for the resulting
> compiler binaries.  I don't understand why the
> process_install_dir_bin_symlinks function is necessary, as cygport
> should already fix up symlinks in the install dir.  I did enable the
> test suite and it tests with 259 fails (was 180 fails before and looks
> about the same general pattern as with version 9.0.1).
>

Without process_install_dir_bin_symlinks, you can't get an installable
package *.xz.
For simplicity, I personally think to put all llvm related packages in
an all-in-one "llvm" package is a good idea.
The new llvm package is going to replace the old clang and llvm, and
maybe other llvm related packages.

  reply	other threads:[~2024-01-16  5:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 12:56 徐持恒 Xu Chiheng
2024-01-10 17:03 ` ASSI
2024-01-10 23:14   ` 徐持恒 Xu Chiheng
2024-01-10 23:16     ` 徐持恒 Xu Chiheng
2024-01-14 20:51   ` ASSI
2024-01-16  5:19     ` 徐持恒 Xu Chiheng [this message]
2024-01-16  6:52       ` ASSI
     [not found]       ` <65a627e8.050a0220.f8b5.ccc4SMTPIN_ADDED_BROKEN@mx.google.com>
2024-01-16  9:34         ` 徐持恒 Xu Chiheng

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='CAPOVtOubMeUkub2V40GFJq0ad5Nqp5-s8cAC6aTF79p+V-=wkg@mail.gmail.com' \
    --to=chiheng.xu@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=cygwin-apps@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).