[SERVER-23200] Where did --enable-new-dtags come from in the ppc64le build Created: 17/Mar/16 Updated: 19/Jul/16 Resolved: 12/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 12 (04/01/16), Platforms 17 (07/15/16) |
| Participants: |
| Description |
|
Where did --enable-new-dtags come from? Or the rpath /usr/lib64/perl5 thing come from? They aren't anywhere in our SConscript, or the evergreen.yml file, yet they appear on the build line. |
| Comments |
| Comment by Githook User [ 12/Jul/16 ] | |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: | |
| Comment by Jonathan Reams [ 17/Mar/16 ] | |
|
This behavior is certainly unexpected, but seems to be the normal way to link against net-snmp on this version/distro of Linux. | |
| Comment by Jonathan Reams [ 17/Mar/16 ] | |
|
These actually come from the enterprise module linking against netsnmp. We call net-snmp-config --agent-libs to get the flags to link against net-snmp, and on rhel71 ppc64le, that adds
|