public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
	小さい猫 <chiisaineko@protonmail.com>
Subject: Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust
Date: Sun, 30 Jul 2023 22:37:46 +0100	[thread overview]
Message-ID: <d2cae911-e668-b5d6-8ac4-3ec6511663fe@dronecode.org.uk> (raw)
In-Reply-To: <bGAGjDxd5DB7JTlfRwHSeHHNT7s_RSEyiY-VLdkwaPunFRwBvWQqjtdAUGXNH0D-_ftbRuPGeBgxZNoLsTyqcLihZ9ROF5kA85MfzH52vnk=@protonmail.com>

On 27/07/2023 07:46, 小さい猫 via Cygwin-apps wrote:
> Hello.
> 
> Recently, for my personal needs, I have been trying to tweak and upgrade the following packages: llvm, compiler-rt, libunwind, libcxxabi, libcxx, clang (upgrading version by version from the original 9.0.1, and currently upgraded to version 12.0.1).
> 
> I imported some useful patches from Fedora RPMs, MinGW packages from MSYS2, and okuoku's llvm fork[1].
> 
> For patches and modified cygport files, the repos are here: https://github.com/orgs/ookiineko-cygpkg/repositories (commit histories are preserved).

Thanks.  This is awesome (and long needed!) work.

I'd suggest, if possible, you try to upstream your patches, as you are 
likely to get more knowledgable review there, but we'll try to take a 
look at them...

I would like to ask why you've dropped debuginfo package generation, and 
why LLVM_CONFIG_PATH needs explicitly setting, in most packages?

  reply	other threads:[~2023-07-30 21:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  6:46 小さい猫
2023-07-30 21:37 ` Jon Turney [this message]
2023-08-02  4:32   ` 小さい猫
2023-12-14  6:42     ` 小さい猫
2024-01-15 10:37       ` 小さい猫
2024-01-15 11:47         ` Takashi Yano
2024-01-15 13:47           ` 小さい猫
2024-01-16 16:44             ` 小さい猫
2024-01-15 17:41         ` ASSI
2024-01-16 11:14           ` 小さい猫
2024-01-21 20:37             ` ASSI
2023-08-13 16:50 ` ASSI
2023-08-14 18:39   ` ASSI
2023-08-18  0:59   ` 小さい猫
2023-08-18  1:11     ` 小さい猫
2023-08-18  4:30     ` ASSI
2023-08-18  7:46   ` 小さい猫
2023-08-26 19:40     ` ASSI
2023-08-27 16:28   ` ASSI
2023-08-28  2:26     ` 小さい猫
2023-08-28 17:58       ` ASSI
2023-08-30  2:18         ` William Hu
2023-08-30 12:16           ` William Hu
2023-08-30 16:31           ` ASSI
2023-09-05 13:47             ` William Hu
2023-09-05 16:11               ` ASSI
2023-09-05 16:13           ` ASSI

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=d2cae911-e668-b5d6-8ac4-3ec6511663fe@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=chiisaineko@protonmail.com \
    --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).