Bug 20727 – `make -f posix.mak clean` requires a D compiler

Status
REOPENED
Severity
normal
Priority
P3
Component
dmd
Product
D
Version
D2
Platform
All
OS
Linux
Creation time
2020-04-10T03:41:37Z
Last change time
2024-12-13T19:08:03Z
Assigned to
No Owner
Creator
Mathias LANG
Moved to GitHub: dmd#19689 →

Comments

Comment #0 by pro.mathias.lang — 2020-04-10T03:41:37Z
Currently, running `make -f posix.mak clean` errors out if one doesn't have `dmd` in the path, because the check in in `src/posix.mak` is done regardless of the target. However, the clean target doesn't depend on DMD. See https://github.com/dlang/dmd/blob/05388e29001a83d1ef47f951433528ea8cf3332c/src/posix.mak#L79-L100 This also broke `setup.sh` from the tools repository, which was one of the pain point of Andrei: https://forum.dlang.org/post/[email protected]
Comment #1 by dlang-bot — 2020-04-10T03:46:49Z
@Geod24 created dlang/tools pull request #399 "Work around issue 20727 by passing BOOTSTRAP when doing clean" mentioning this issue: - Work around issue 20727 by passing BOOTSTRAP when doing clean As explained in issue 20727, AUTO_BOOTSTRAP is not required for 'clean', but still triggers the error. https://github.com/dlang/tools/pull/399
Comment #2 by dlang-bot — 2020-04-10T04:21:12Z
dlang/tools pull request #399 "Work around issue 20727 by passing BOOTSTRAP when doing clean" was merged into master: - 895d01aac8cc7247f9573289b0c181de16901047 by Geod24: Work around issue 20727 by passing BOOTSTRAP when doing clean As explained in issue 20727, AUTO_BOOTSTRAP is not required for 'clean', but still triggers the error. https://github.com/dlang/tools/pull/399
Comment #3 by pro.mathias.lang — 2020-05-05T17:43:59Z
@Razvan: Why did you close? The linked PR is a workaround in tools, for a bug in DMD, and I didn't see any PR addressing it recently.
Comment #4 by razvan.nitu1305 — 2020-05-08T07:42:16Z
Sorry, I thought the issue was fixed.
Comment #5 by robert.schadek — 2024-12-13T19:08:03Z
THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/19689 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB