From: 小さい猫 <chiisaineko@protonmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [Sharing progress] Tried to revive LLVM/Clang/Libc++ pkgs and port Rust
Date: Thu, 14 Dec 2023 06:42:29 +0000 [thread overview]
Message-ID: <R_mkC0YFunTZyNtxKUp35YGa6cfV-qlO1-rmMCuBx9qPO7pQaYOLUC6iOjBFRbyw0TX63yjeAnQacTVdpBEyL35PDafh8ns4xLm5vc2VIzA=@protonmail.com> (raw)
In-Reply-To: <bj62Yj82RDXacGVZFbwOQt4lrra0y5M7dh0Q--2-4dsfatbTtx4q4INbxkFM-hf1RdioEUTwThrtL1w3up17ZAqkaGASLlfx9Ci8MPxizjE=@protonmail.com>
On Wednesday, 2 August 2023 at 12:32 PM, 小さい猫 <chiisaineko@protonmail.com> wrote:
> On Monday, July 31st, 2023 at 5:37 AM, Jon Turney jon.turney@dronecode.org.uk wrote:
>
> > why LLVM_CONFIG_PATH needs explicitly setting, in most packages?
>
> LLVM_CONFIG_PATH is there as a template, when building the next version, i will manually set them to something like $HOME/llvm/llvm-x.y.z-a.arch/inst/usr/bin/llvm-config.
>
> But maybe that is not the correct way to build it.
it turned out it's not necessary, the correct build order is (i think): llvm -> clang -> compiler-rt -> libunwind -> libcxx (with the previous version of libcxxabi) -> libcxxabi -> libcxx
By the way, just now I have updated these cygports to 13.0.1 LLVM release in my GitHub repo.
next prev parent reply other threads:[~2023-12-14 6:42 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 ` 小さい猫 [this message]
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='R_mkC0YFunTZyNtxKUp35YGa6cfV-qlO1-rmMCuBx9qPO7pQaYOLUC6iOjBFRbyw0TX63yjeAnQacTVdpBEyL35PDafh8ns4xLm5vc2VIzA=@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).