This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: gcc-3.2 build problem in the java area
- From: Russ Allbery <rra at stanford dot edu>
- To: java at gcc dot gnu dot org
- Date: Fri, 11 Oct 2002 10:38:39 -0700
- Subject: Re: gcc-3.2 build problem in the java area
- Organization: The Eyrie
- References: <Pine.GSO.4.21.0210101047230.21396-100000@obrien.cc.rochester.edu><15781.38525.112250.301901@cuddles.cambridge.redhat.com><ylk7kphf29.fsf@windlord.stanford.edu><15782.49167.813960.608230@cuddles.cambridge.redhat.com><87r8ewgb8h.fsf@fleche.redhat.com>
Tom Tromey <tromey@redhat.com> writes:
> Is __EXTENSIONS__ really the thing to define?
> Or does this get defined as the result of defining some macro we're
> supposed to define?
If it's defined by something else, I can't find it, and the man page on
Solaris says:
Feature Test Macros
[...]
If the application is using interfaces and headers not defined by
that standard, then in addition to defining the appropriate standard
feature test macro, it must also define __EXTENSIONS__. Defining
__EXTENSIONS__ provides the application with access to all interfaces
and headers not in conflict with the specified standard. The
application must define __EXTENSIONS__ either at compile time or
within the application.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>