make --question fails
Bug #1669891 reported by
mdavidsaver
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EPICS Base |
Fix Released
|
Low
|
mdavidsaver | ||
3.14 |
Fix Released
|
Low
|
Andrew Johnson | ||
3.15 |
Fix Released
|
Low
|
Andrew Johnson | ||
3.16 |
Fix Released
|
Low
|
Martin Konrad |
Bug Description
With a template created by makeBaseApp, attempting to run make in "question" mode gives an error under configure/ which prevents this feature from being useful. The error message is a bit mystifying.
Changed in epics-base: | |
milestone: | 3.16.1 → 7.0.2 |
status: | Confirmed → Fix Committed |
Changed in epics-base: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is something to do with RELEASE checking. If I can successfully run
> make CHECK_RELEASE=NO CHECK_RELEASE_NO= -q
The "CHECK_RELEASE_NO=" is necessary, which avoids unconditional execution of an "@echo". So to support --question may require avoiding any unconditional execution (including genVersionHeade r.pl).
Do we want to support --question?
As background. FRIB would like to use this in combination with Puppet to decide if an IOC process should be rebuilt/restarted.