gnetlist bom & bom2 backends don't exit with non-zero status when fail
Bug #1256435 reported by
Vladimir Zhbanov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gEDA |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When an error occurs (if the necessary "attribs" file is missing),
bom & bom2 backends output some description for it but the
gnetlist exit status is 0. It shouldn't be zero to effectively use
gnetlist in scripts or Makefiles.
Revision history for this message
| Vladimir Zhbanov (vzhbanov) wrote | #1 |
Revision history for this message
| Vladimir Zhbanov (vzhbanov) wrote | #2 |
Revision history for this message
| Edward Hennessy (ehennes) wrote | #3 |
| Changed in geda: | |
| status: | New → Fix Committed |
| Changed in geda: | |
| milestone: | none → 1.9.1 |
| Changed in geda: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
To reproduce the bug, make a directory, cd to it, make or copy any
schematic there, and type
gnetlist -g bom your_schematic.sch; echo $?
There must be no "attribs" file there.
The same for bom2.