小さい猫 via Cygwin-apps writes:
> now updated to 15.0.7
I've built it and activated the tests, which seem to have roughly the
same results as 9.0.1, so that looks good.
For 9.0.1 I think I've finally got it to build almost cleanly. I still
need to ignore some fallout from documentation bitrot, but
On Monday, 15 January 2024 at 9:47 PM, 小さい猫 wrote:
> me too, i have already compiled llvm15, so the next is clang and libc++
> blabla...
On Tuesday, 16 January 2024 at 7:14 PM, 小さい猫 via Cygwin-apps
wrote:
> now updated to 15.0.7
so i have moved back to linux and started to continue trying
On Tuesday, 16 January 2024 at 1:41 AM, ASSI via Cygwin-apps
wrote:
> THanks for letting us know. I can't promise, but I'll try to have a look over
> the weekend.
<3
On Monday, 15 January 2024 at 6:37 PM, 小さい猫 wrote:
> now updated to 14.0.5
now updated to 15.0.7
小さい猫 via Cygwin-apps writes:
> On Thursday, 14 December 2023 at 2:42 PM, 小さい猫 via Cygwin-apps
> wrote:
>
>> By the way, just now I have updated these cygports to 13.0.1 LLVM release in
>> my GitHub repo.
>
> now updated to 14.0.5
THanks for letting us know. I can't promise, but I'll try to
On Monday, 15 January 2024 at 7:47 PM, Takashi Yano
wrote:
> I'm really looking forward to Rust running on cygwin.
me too, i have already compiled llvm15, so the next is clang and libc++
blabla...
> BTW, are you aware of this ITA?
>
On Mon, 15 Jan 2024 10:37:23 +
小さい猫 wrote:
> On Thursday, 14 December 2023 at 2:42 PM, 小さい猫 via Cygwin-apps
> wrote:
>
> > By the way, just now I have updated these cygports to 13.0.1 LLVM release
> > in my GitHub repo.
>
> now updated to 14.0.5
I'm really looking forward to Rust running
On Thursday, 14 December 2023 at 2:42 PM, 小さい猫 via Cygwin-apps
wrote:
> By the way, just now I have updated these cygports to 13.0.1 LLVM release in
> my GitHub repo.
now updated to 14.0.5
On Wednesday, 2 August 2023 at 12:32 PM, 小さい猫
wrote:
> On Monday, July 31st, 2023 at 5:37 AM, Jon Turney jon.tur...@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
William Hu via Cygwin-apps writes:
> Hi All,
>
> Re OCaml compilers: I should be able to package OCaml 4.14.1 (and hopefully
> an
> alpha version of 5.1.0 as well) for Cygwin in the coming weeks. OCaml 5.0.0
> temporarily dropped Cygwin support so the Cygwin versions will of course skip
> that
William Hu via Cygwin-apps writes:
> On Wednesday, August 30th, 2023, ASSI wrote:
>> NOt immediately, but it makes me wonder if there's other such leakage.
>> I have not found a (text) file that stores this information in the
>> installed package, so it seems that the information is compiled in
>>
On Wednesday, August 30th, 2023, ASSI wrote:
> NOt immediately, but it makes me wonder if there's other such leakage.
> I have not found a (text) file that stores this information in the
> installed package, so it seems that the information is compiled in
> someplace.
After some digging I believe
William Hu via Cygwin-apps writes:
> Just checked the file and I agree that CFLAGS looks a little funny - are
> there any
> other stupid flags/variables that you had in mind?
NOt immediately, but it makes me wonder if there's other such leakage.
I have not found a (text) file that stores this
On Tuesday, August 29th, 2023 at 10:18 PM, William Hu wrote:
> src_test:
> 1. I believe "make ocamltest" does not run the testsuite; AFAIU, it builds the
> auxiliary testing software instead. So far the only ways I know of to run the
> testsuite are either "make tests" or cd'ing into the testsuite
Hi All,
Re OCaml compilers: I should be able to package OCaml 4.14.1 (and hopefully an
alpha version of 5.1.0 as well) for Cygwin in the coming weeks. OCaml 5.0.0
temporarily dropped Cygwin support so the Cygwin versions will of course skip
that release.
On Saturday, August 26th, 2023 at 3:40
小さい猫 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].
OK, I thought so already, but I
Thank you for your hard work <3
On Monday, August 28th, 2023 at 12:28 AM, ASSI via Cygwin-apps
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
ASSI via Cygwin-apps writes:
> I've started a local llvm-revival branch…
Progress, OCaml bindings are back again (I've not run the tests yet):
--8<---cut here---start->8---
* OCaml Updates
- [X] flexdll 0.39 ==> 0.43
+ does not recognize -pthread, but
小さい猫 via Cygwin-apps writes:
> i am not familiar with the ocaml stuffs, and i dont quite understand
> what is the problem ur currently getting.
Dune cannot be fully built because lwt.unix or one of it's dependencies
is missing. I could built a bootstrapped package, but that later runs
into
On Monday, August 14th, 2023 at 12:50 AM, ASSI via Cygwin-apps
wrote:
> - ocaml-dune
> + no longer builds with the original recipe, missing external libraries that
> in turn require dune to build
> + bootstrapped dune should still be viable
> - ocaml-ctype
> + would be needed for llvm
> +
小さい猫 via Cygwin-apps writes:
> On Monday, August 14th, 2023 at 12:50 AM, ASSI via Cygwin-apps
> wrote:
>
>> I've started a local llvm-revival branch… I got sidetracked with OCaml,
>> but that will need some more time and currently I have just disabled the
>> OCaml bindings in LLVM instead (not
On Friday, August 18th, 2023 at 8:59 AM, 小さい猫 via Cygwin-apps
wrote:
> also starting from llvm 11, libunwind seemed to use some asm and the build
> bugged due a cmake bug(?)
the cmake issue is about to remove -fPIC from the asmflags.
starting from llvm12, msys2/mingw introduced a patch to
On Monday, August 14th, 2023 at 12:50 AM, ASSI via Cygwin-apps
wrote:
> I've started a local llvm-revival branch… I got sidetracked with OCaml,
> but that will need some more time and currently I have just disabled the
> OCaml bindings in LLVM instead (not removed: this is controlled by a
>
ASSI via Cygwin-apps writes:
> I've started a local llvm-revival branch… I got sidetracked with OCaml,
> but that will need some more time and currently I have just disabled the
> OCaml bindings in LLVM instead (not removed: this is controlled by a
> variable in the script and another variable to
I've started a local llvm-revival branch… I got sidetracked with OCaml,
but that will need some more time and currently I have just disabled the
OCaml bindings in LLVM instead (not removed: this is controlled by a
variable in the script and another variable to control the LLVM target
list).
On Monday, July 31st, 2023 at 5:37 AM, Jon Turney
wrote:
> I would like to ask why you've dropped debuginfo package generation, and
> why LLVM_CONFIG_PATH needs explicitly setting, in most packages?
just because my laptop doesn't have much storage left for Windows...
LLVM_CONFIG_PATH is there
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
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
27 matches
Mail list logo
