[SERVER-10305] libdeps system no longer correctly detecting and printing dependency cycles Created: 23/Jul/13 Updated: 14/Apr/16 Resolved: 27/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Jonathan Reams |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Tested with SCons 2.1.0 (from Andy's repo) and 2.3.0 (from local machine) |
||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Create a libdeps cycle, and compile. |
||||||||
| Sprint: | BUILD 1 | ||||||||
| Participants: | |||||||||
| Description |
|
If you create a libdeps dependency cycle, instead of getting a helpful error message describing the cycle, you get a truncated link line and lots of linker errors, which makes it hard to track down the cycle. |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 27/Jan/15 ] |
|
Dup of |