Alexey Vyskubov
Alexey Vyskubov
Can you point me to the PR, please? I've just hit the same error (and this bug is over one month old).
So PR was merged, and my error changed to ``` [blah] [2 of 2] Compiling Paths_space_age Linking .stack-work/dist/x86_64-linux-tinfo6/Cabal-3.6.3.0/build/test/test ... collect2: error: ld returned 1 exit status `gcc' failed in phase...
...and now I cannot build locally anymore with `clock > error: gcc: error: unrecognized command-line option '--target=x86_64-portbld-freebsd--lflag=--target=x86_64-portbld-freebsd'`. Isn't the space missing before `--lflag`?
How my system information relates to `ld` failure at Exercism site (see above)? The fact that local build started to fail is just an additional information and can be ignored.
Yes, it looks like linker error on exercism site was fixed. My tests passed.
and just FYI: I have fixed the local build by switching `ghc` from the usage of `gcc` to the usage of `clang`. Quite possible that `gcc` in FreeBSD is broken...
I no longer see this exception. I have another problem but it is in a separate issue. I did not try net 7 yet, which, according to my knowledge, was...
I've hit a problem very similar to yours, and I think I know the reason. Look here: https://github.com/vandium-io/aws-param-store/blob/00c426239376c3b0ec901e971af9fb96c601b96f/lib/param_query.js#L125 What the code tries to do is to spawn another node process...
`:Files` preview in `gvim.exe` is slightly better, though docstring is still invisible:
vcxsrv + X tunneling over ssh from FreeBSD 13.1 -- expected colors in preview.