On Tue, 2013-07-02 at 20:49 +0000, Joseph S. Myers wrote: > On Tue, 2 Jul 2013, David Malcolm wrote: > > > So I envisage a "--enable-shared" configuration switch to opt-in to the > > shared library code, but I want as minimize the difference between the > > two cases. > > --enable-host-shared or --enable-shared-gcc or some other such option > name, please, not plain --enable-shared with currently refers to the > libraries built for the target. Whether the target libraries should be > shared libraries is a choice completely independent of whether to build > GCC itself as a shared library
Good catch; thanks. I've added a note on this to my plan doc. [1] > (or libraries? - since you have lots of > separate front ends that don't currently expect to be linked together, > although actually making it possible to link them together is probably > only a few days' work). I think a lot of this will be dependent on Andrew's big frontend vs backend cleanup, but yes, multiple libraries would be much nicer. Thanks Dave [1] https://github.com/davidmalcolm/gcc-global-state/commit/a5bf16116a6da217981a9c94f8f999fec995dfc7
