[SERVER-11689] When linking with libstdc++ statically, also link with libgcc statically Created: 13/Nov/13 Updated: 11/Jul/16 Resolved: 27/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | build | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
When statically linking libstdc++ in an effort to be able to run on systems with older system libstdc++ installed, it is important to also link libgcc statically. However, our --static-libstdc++ flag only causes libstdc++ to be linked statically. Our interpretation of that flag should imply --static-libgcc as well. |
| Comments |
| Comment by Githook User [ 27/Nov/13 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}Message: |
| Comment by Ernie Hershey [ 22/Nov/13 ] |
|
I verified that building mongod with this change, using gcc 4.8.2 built with --disable-gnu-unique-object runs successfully in fedora 8. |