This is the mail archive of the gcc@gcc.gnu.org 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] |
Hello! It is currently unclear whether GNU/Hurd, GNU/k*BSD, or GNU/* in general should share stuff (like configuration branches inside `config.gcc', files from `config/') with GNU/Linux. This is -- because of the targets being pretty much similar -- how it used to be done in the past. But now GCC's Andrew Pinski indicated that this shall no longer be desired, for example in <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28102>. Contrary to Andrew, I would vote for all those GNU/* targets sharing the same configuration machinery, as they are indeed meant to be as close to each other as possible. To give an example: all the GNU/* configurations use the `config/linux.h' file, even though only one of the possible GNU/* configurations is actually a Linux one. Additionally the non-Linux ones currently have files like `config/gnu.h' (for GNU/Hurd) or `config/kfreebsd-gnu.h' (for GNU/kFreeBSD) to customize what is different for them from the main Linux configuration file. To state this intended similarity clearly, one could rename, e.g., `config/linux.h' to `config/gnu-shared.h' and then have a new (nearly empty) file `config/linux.h' additionally to the existing `config/gnu.h', `config/kfreebsd-gnu.h', etc. to do the remaining few customizations. I'd offer (and already began) to work on this. Please comment. Regards, Thomas
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |