View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
---|---|---|---|---|---|---|---|---|---|
0000287 | mercury | Bug | public | 2013-05-28 12:55 | 2013-06-05 16:02 | ||||
Reporter | wangp | ||||||||
Assigned To | juliensf | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | resolved | Resolution | fixed | ||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0000287: configure requires m4 | ||||||||
Description | The configure script expects m4 to be present: m4 -DDEFAULT_MERCURY_DEBUGGER_INIT_DIR=TESTS_MDB_INIT_DIR \ -DDEFAULT_MERCURY_DEBUGGER_DOC=TESTS_MDB_DOC \ "`pwd`"/scripts/mdbrc.in > $test_mdbrc.in | ||||||||
Tags | No tags attached. | ||||||||
Attached Files |
|
Notes | |
juliensf (administrator) 2013-05-28 13:44 |
We could just skip the above if m4 is not present. What it's doing is only critical to running the test suite, so in principle an installation should be able to proceed without it. |
pbone (administrator) 2013-05-28 15:15 |
Or have this executed from the test suite's Makefile. |
juliensf (administrator) 2013-05-28 15:21 |
Or what Paul says. This is a fairly recent problem since before we moved to git we would only have executed the above if the tests directory was present. |
juliensf (administrator) 2013-06-05 16:02 |
Fix committed. |
Issue History | |||
Date Modified | Username | Field | Change |
---|---|---|---|
2013-05-28 12:55 | wangp | New Issue | |
2013-05-28 13:44 | juliensf | Note Added: 0000528 | |
2013-05-28 15:15 | pbone | Note Added: 0000530 | |
2013-05-28 15:21 | juliensf | Note Added: 0000531 | |
2013-06-05 15:52 | juliensf | Assigned To | => juliensf |
2013-06-05 15:52 | juliensf | Status | new => assigned |
2013-06-05 16:02 | juliensf | Note Added: 0000534 | |
2013-06-05 16:02 | juliensf | Status | assigned => resolved |
2013-06-05 16:02 | juliensf | Resolution | open => fixed |