This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Plugins always enabled in GCC 4.8?

Hello All,

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). 

In that case, I think that we should always --enable-plugin at configure time, hence
making that configure switch useless (since always on).

What do you think?

Do we aim at running next GCC on systems without dynamic libraries or withour plugins?
(If yes, why and which ones)?

Likewise, I also hope that next GCC will be only C++ compilable (and that we remove the
ability to compile it with C)

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?

email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]