leanprover / leanprover/fp-lean

`lake exe fp-lean` fails with `bash: doug: command not found` and `Non-zero exit code from 'sort --shared < test-data'`

Open
#191 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lean
Stars
192
Forks
73
PR merge metrics
No merged PRs in 30d

Description

lake exe fp-lean fails with bash: doug: command not found and Non-zero exit code from 'sort --shared < test-data':

% git clone https://github.com/leanprover/fp-lean
% cd fp-lean
% lake exe fp-lean
✖ [336/348] Building FPLean.MonadTransformers.ReaderIO
error: FPLean/MonadTransformers/ReaderIO.lean:31:0: Non-zero exit code from 'doug' (127).
  Stdout:
  Stderr:
    bash: doug: command not found
error: Lean exited with code 1
✖ [340/348] Building FPLean.ProgramsProofs.InsertionSort
error: FPLean/ProgramsProofs/InsertionSort.lean:785:0: Mismatched commands output:
  $ expect -f ./run-usage # sort
- Expected single argument, either "--shared" or "--unique"
…
error: FPLean/ProgramsProofs/InsertionSort.lean:818:0: Non-zero exit code from 'sort --shared < test-data' (2).

Environment:

% sw_vers
ProductName:		macOS
ProductVersion:		15.1.1
BuildVersion:		24B2091
% which doug
doug not found
% which sort
/usr/bin/sort

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce lake exe fp-lean on the reported macOS environment, then inspect FPLean/MonadTransformers/ReaderIO.lean at line 31 and FPLean/ProgramsProofs/InsertionSort.lean at lines 785 and 818. Compare the doug and sort --shared failures with the project’s expected command setup; done means the build completes without these errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.