Ticket #1458 (closed RFC: fixed)

Opened 5 years ago

Last modified 4 years ago

Don't add probed warnings to config information.

Reported by: coke Owned by:
Priority: normal Milestone:
Component: none Version: 2.1.0
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

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:

./parrot_config ccwarn

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.

Change History

Changed 5 years ago by Austin_Hastings

It seems to me that if you're asking config questions, you are likely to be asking:

1. Show me the flags you built with. If you had different flags for different files (why?) then show me those.

2. Give me the set of flags that XX was built with, so I can build YY with the same.

Beyond that, I don't think there's much value in providing any other data.

Changed 5 years ago by coke

  • owner set to coke

Changed 5 years ago by coke

  • owner coke deleted

Changed 4 years ago by coke

  • status changed from new to closed
  • resolution set to fixed

looks like the probed warnings are gone.

Note: See TracTickets for help on using tickets.