public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: 小さい猫 <chiisaineko@protonmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust
Date: Mon, 28 Aug 2023 02:26:07 +0000	[thread overview]
Message-ID: <d-yrLbGwl-psQ9AAaazcIv93VAikjwbHPrbR9kKEn2iGPH4vS9-sF1Ya5Pwa1TfAv-wXpLgOTKn1WkwFNTM4Mu6t3MvXlWFa3Qex2PvJfzU=@protonmail.com> (raw)
In-Reply-To: <87sf84sb3u.fsf@Rainer.invalid>

Thank you for your hard work <3

On Monday, August 28th, 2023 at 12:28 AM, ASSI via Cygwin-apps <cygwin-apps@cygwin.com> wrote:

> ASSI via Cygwin-apps writes:
> 
> - [ ] dtc (?)

Ah sorry... that device tree compiler cygport repo in the github org is not related to LLVM stuffs. just i happened to need it for building something else and it's adapted from the old cygwinports-extras[1].

[1]: https://github.com/cygwinports-extras/dtc

  reply	other threads:[~2023-08-28  2:26 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
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     ` 小さい猫 [this message]
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='d-yrLbGwl-psQ9AAaazcIv93VAikjwbHPrbR9kKEn2iGPH4vS9-sF1Ya5Pwa1TfAv-wXpLgOTKn1WkwFNTM4Mu6t3MvXlWFa3Qex2PvJfzU=@protonmail.com' \
    --to=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).