You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While building Revery on macOS 10.14.6 (Mojave), esy install worked just fine, but I encountered this error (text file) while running esy 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:
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
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:esy-sdl2/Makefile.in
Line 126 in 0935dbf
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.The text was updated successfully, but these errors were encountered: