View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003935 | unreal | installing | public | 2010-07-15 23:49 | 2010-07-16 14:04 |
Reporter | ohnobinki | Assigned To | ohnobinki | ||
Priority | normal | Severity | trivial | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Product Version | 3.2.8 | ||||
Fixed in Version | 3.2.9-RC1 | ||||
Summary | 0003935: user-friendly `make custommodule' errors | ||||
Description | An often-heard question in #unreal-support is how to properly use `make custommodule'. I think that the following output would be more useful: peter-krakers-mac-mini:unreal zoidberg$ make custommodule m_mymodule Please set MODULEFILE when calling ``make custommodule''. For example, ``make custommodule MODULEFILE=callerid''. make: *** [custommodule] Error 1 peter-krakers-mac-mini:unreal zoidberg$ I'm sure that the output could be made cleaner, though. And the patch only supports the simple case of MODULEFILE not being set. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
3rd party modules | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2010-07-15 23:49 | ohnobinki | New Issue | |
2010-07-15 23:49 | ohnobinki | File Added: unreal-make-custommodule-error.patch | |
2010-07-15 23:49 | ohnobinki | QA | => Not touched yet by developer |
2010-07-15 23:49 | ohnobinki | U4: Need for upstream patch | => No need for upstream InspIRCd patch |
2010-07-15 23:49 | ohnobinki | U4: Upstream notification of bug | => Not decided |
2010-07-15 23:49 | ohnobinki | U4: Contributor working on this | => None |
2010-07-16 13:14 | syzop | Note Added: 0016208 | |
2010-07-16 14:04 | ohnobinki | Note Added: 0016209 | |
2010-07-16 14:04 | ohnobinki | Status | new => resolved |
2010-07-16 14:04 | ohnobinki | Fixed in Version | => 3.2.9-RC1 |
2010-07-16 14:04 | ohnobinki | Resolution | open => fixed |
2010-07-16 14:04 | ohnobinki | Assigned To | => ohnobinki |