On 3/31/12 1:51 PM, Basile Starynkevitch wrote:
If we want to aim towards a more modular GCC made of several shared libraries, it seems that we are requiring the host system to have dynamic libraries (which is not a big deal today; all the major OSes running on developers desktop or laptop have them).
I don't follow. Modularity does not require shared libraries.
In that case, I think that we should always --enable-plugin at configure time, hence making that configure switch useless (since always on).
Plugins are auto-detected on systems that support it and always enabled.
Likewise, I also hope that next GCC will be only C++ compilable (and that we remove the ability to compile it with C)
This will only happen if someone does the work. Hope produces no patches.
More generally, I would like a description, or a list of host systems for GCC. What kind of system services [e.g. dlopen, time, ...] to we require GCC to access to?
The plugin support detection already asks these questions to the host system.
Diego.
