Fix configure infinite loop (corner cases) for autoconf projects caused by --dry-run+--always-make
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- build-system, tooling
Research direction
No source file or test is identified in the issue. Start by reproducing the configure infinite loop in an autoconf project with --dry-run and --always-make, then inspect how the Makefile Tools extension invokes make and handles recursive makefiles. Done means the corner cases no longer loop while existing configure behavior remains intact.
Written by the indexing model from the issue text.
Description
@drok , thank you for the additional info, very useful and we will consider it all. Lucky that indeed the most common cases can be addressed with the simpler approach. I will open a work item for the cases that we will not be able to address, including an eventual fork of make or even a contribution into the main one, if it will be desired.
Brainstorm: I am not familiar yet with automake to write myself or play much with it other than just run the usual commands on an existing framework. Can you see a solution where the Makefile Tools extension would use the original makefile of the project as source-input, we call automake ourselves to generate a new makefile which will be identical in content but at least can inherit the variables we need? Then the dry-run will be invoked on that newly generated makefile. I'll be thinking and maybe you can also add on top of this idea or let me know if you see this wouldn't help at all.
Or... We could also with some easy preprocess string manipulation change all the recursive MAKE invocations from the source-input makefiles so that all the destination-output makefiles automake (the one ran by us) have the right flags inserted at the end of the command... This is just brainstorm for future...
Originally posted by @andreeis in https://github.com/microsoft/vscode-makefile-tools/issues/500#issuecomment-1745347632
- Dominant language
- TypeScript
- Stars
- 243
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-makefile-tools
-
Dry-run during configure executes workspace recipes and can terminate VS Code (kill 0 in a Makefile trap)Possibly taken @JoakimCarlsson claimed this 21 days ago. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 62/100
microsoft/vscode-makefile-tools#835 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/vscode-makefile-tools#825 · 2 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
[Feature] Makefile Tools output window should automatically open when running makefile commandsOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/vscode-makefile-tools#759 · 1 comment · 1 reaction ·
All issues in microsoft/vscode-makefile-tools
Similar issues
-
[bug] diagnostics.dumpBody：Buffer 形态请求（透传 lane）跳过 dumps/ 落盘，仅留 raw/-unknown-Possibly taken @ranxianglei claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ranxianglei/billion-context#2421 · 2 comments ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nuxt/test-utils#1842 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
MoonshotAI/kimi-code#4146 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
farbenmeer/tapi#531 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day