That sounds right to me.
On Mon, Jan 17, 2022 at 9:27 AM Nathaniel W Griswold wrote:
> Ah, ok, my build finished and everything seems to be working well. The
> binary is signed, too. It seems to have used codesign.rkt along the way
> there, so i think i actually needed both Matthew's recommended
Ah, ok, my build finished and everything seems to be working well. The binary
is signed, too. It seems to have used codesign.rkt along the way there, so i
think i actually needed both Matthew's recommended commit and yours
(codesign.rkt imports compiler/private/mach-o). Does that sound right, to
That particular issue is fixed by
https://github.com/racket/racket/commit/3a8a7102abff334ee4e054c3597bebba32bda307,
if I remember correctly.
On Mon, Jan 17, 2022 at 8:50 AM Nathaniel W Griswold wrote:
> Hm, Ok. The cherry-pick of 0a8b68b286 does in fact apply cleanly to the
> v8.3 tag.
>
> I am
Hm, Ok. The cherry-pick of 0a8b68b286 does in fact apply cleanly to the v8.3
tag.
I am still having the same issue, though, even after a full clean. Right now, I
only have command-line tools (latest). I am downloading the full Xcode again
but it's gonna be a little bit before i can test that, t
This is a problem with v8.3 and the latest Apple tools. It's fixed for
the upcoming v8.4 release (so, in the main branch and in the current
snapshot source distributions).
In case you want a minimal patch, commit 0a8b68b286 is the repair and
might apply cleanly to v8.3.
At Mon, 17 Jan 2022 10:16:
What version of Xcode do you have? Assuming it's the latest, have you
opened it at least once to go through the first run setup of CLI tools?
- Ryan
On Mon, 17 Jan 2022 at 16:16, Nathaniel W Griswold wrote:
> Has anyone else run into this error (see below) when building natively on
> Apple sili
6 matches
Mail list logo