Open ron-wolf opened 3 years ago
Any guidance on how to test this would also be helpful. I tried the obvious solution of changing the Makefile in-place, but the Esy build system (which I’m unfamiliar with) keeps overwriting it. Would I have to create a fork/branch and use that as a temporary replacement dependency? @bryphe
If anyone else comes upon this issue, the status is best explained here: https://github.com/onivim/oni2/issues/3811#issuecomment-910306404
While building Revery on macOS 10.14.6 (Mojave),
esy install
worked just fine, but I encountered this error (text file) while runningesy build
. Here is how the end of console output appeared on my screen in Terminal.app:Click to reveal tall image
I tracked the issue down to the following line introduced to the Makefile in 5e162af, where
fgrep
is run but for some reason emits color codes on my machine:https://github.com/revery-ui/esy-sdl2/blob/0935dbf8c7a770f61f6041b0af743746c18648da/Makefile.in#L126
Here is my default env before any configuration files are loaded:
And here are the contents of my direnv envrc:
That should account for pretty much everything that would affect the behavior of
fgrep
within a subprocess or subshell.