Ticket #1458 (closed RFC: fixed)
Don't add probed warnings to config information.
|Reported by:||coke||Owned by:|
During configuration, all warnings that are successfully probed are entered into the parrot configuration. So if you built with gcc, you can run:
$ ./parrot_config -Wall 1
This seems like overkill, especially when:
seems sufficient. (ccwarn is empty in trunk, but what you'd expect in the rm_cflags branch.)
Feedback (esp. whether or not this constitutes a deprecation issue) welcome.