This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Identifying the EGCS back-end
On Nov 5, 1998, Peter Gerwinski <peter@gerwinski.de> wrote:
> Alexandre Oliva wrote:
>> Another option is to test for egcs features in config-lang.in,
>> grepping header files or such...
> Yes, that's possible. But I would consider this a non-clean
> solution unless there is something that identifies EGCS without
> any doubt.
As suggested in the manual of autoconf, you should test for the
features you use. If the argument lists have changed, check those
argument lists, so, if some day they change again, instead of failed
compilation at random points, you get a configure-time warning/error
message.
> Hm ... and what shall `config-lang.in' do then? Create yet
> another `.h' file which either contains `#define EGCS' or just
> nothing?
That's an option that is simple enough and works...
> but I can imagine that there is a more elegant solution.
Or maybe some egcs header-file should #define THIS_IS_EGCS. But I
don't think this is more elegant than the alternative :-)
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:oliva@gnu.org mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil