--disable-shared support

--disable-shared support

[Florian Weimer]

--disable-shared has apparently been broken for a long, long time. 
Should we remove any vestiges of support for it?

Thanks,
Florian

Re: --disable-shared support

[Joseph Myers]

On Mon, 25 Jun 2018, Florian Weimer wrote:

> --disable-shared has apparently been broken for a long, long time. Should we
> remove any vestiges of support for it?

I think we should fix this problem (bug 20845), to facilitate 
--disable-shared being used as a way to run the full testsuite for static 
linking.

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: --disable-shared support

[Florian Weimer]

On 06/26/2018 11:07 PM, Joseph Myers wrote:
> On Mon, 25 Jun 2018, Florian Weimer wrote:
> 
>> --disable-shared has apparently been broken for a long, long time. Should we
>> remove any vestiges of support for it?
> 
> I think we should fix this problem (bug 20845), to facilitate
> --disable-shared being used as a way to run the full testsuite for static
> linking.

Is this the only reason for fixing it?

I wonder if we should link and run all tests statically which can run 
statically linked, rather than relying on tests opting in explicitly 
(which some do).

Thanks,
Florian

Re: --disable-shared support

[Joseph Myers]

On Fri, 29 Jun 2018, Florian Weimer wrote:

> I wonder if we should link and run all tests statically which can run
> statically linked, rather than relying on tests opting in explicitly (which
> some do).

I think that's excessive for normal testing, but there should be an easy 
way to run all tests for static linking when desired.

--disable-shared really should only reduce the set of files built and 
installed, and result in some installed and test executables being 
statically linked - it should not have major differences in the build 
process from the default case, and if it does, that sounds like something 
to fix.

-- 
Joseph S. Myers
joseph@codesourcery.com