I wonder if you could arrange things so that you could have statically linked and dynamic linked executable. Kind of like what they do with the Linux kernel. When your installation is configured in such a way as to make the dynamic linking a problem, just compile a version that has (almost) everything bolted in. Otherwise compile the features as modules.
- Re: RFC 146 (v1) Remove socket functions from core Bradley M. Kuhn
- Re: RFC 146 (v1) Remove socket functions from c... Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from core Stephen P. Potter
- Re: RFC 146 (v1) Remove socket functions from core Tom Christiansen
- Re: RFC 146 (v1) Remove socket functions from c... Dan Sugalski
- Re: RFC 146 (v1) Remove socket functions fr... Nathan Torkington
- Re: RFC 146 (v1) Remove socket function... Dan Sugalski
- Re: RFC 146 (v1) Remove socket fun... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket fun... Dan Sugalski
- Re: RFC 146 (v1) Remove socket fun... Alan Burlison
- RE: RFC 146 (v1) Remove socket fun... Al Lipscomb
- RE: RFC 146 (v1) Remove socket fun... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket fun... David L. Nicol
- Re: RFC 146 (v1) Remove socket fun... Nick Ing-Simmons
- Re: RFC 146 (v1) Remove socket fun... David L. Nicol
- Re: RFC 146 (v1) Remove socket fun... Dan Sugalski
- Re: RFC 146 (v1) Remove socket fun... David L. Nicol
- Re: RFC 146 (v1) Remove socket fun... Dan Sugalski
- Re: RFC 146 (v1) Remove socket fun... mooring
- Re: RFC 146 (v1) Remove socket fun... Alan Burlison
- Re: RFC 146 (v1) Remove socket fun... Nick Ing-Simmons