This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: autoconf 2.50 updates - libjava
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: autoconf 2.50 updates - libjava
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 28 May 2001 22:47:58 -0300
- Cc: Zack Weinberg <zackw at Stanford dot EDU>, Tom Tromey <tromey at redhat dot com>, gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org, Anthony Green <green at redhat dot com>
- Organization: GCC Team, Red Hat
- References: <87lmnjlix9.fsf@creche.redhat.com><20010527111124.Z28699@stanford.edu><20010528180601.C14613@disaster.jaj.com>
On May 28, 2001, Phil Edwards <pedwards@disaster.jaj.com> wrote:
> On Sun, May 27, 2001 at 11:11:24AM -0700, Zack Weinberg wrote:
> [on AC_TRY_LINK]
>> The real nasty is libstdc++-v3 which has serious need to run linkage
>> checks (but only with the C compiler, I *think*.)
> I believe this is correct. Lots of checks under C for linkage of math
> functions, plus one test for some LC_MESSAGE-related stuff.
I wonder if we couldn't turn these into compile tests. For example,
we can tell whether a function declared in some header file has C
linkage by trying to overload it with another extern "C" function. If
we get an error back, we know it had been declared as extern "C".
I believe it's reasonable to assume that any function for which we
don't find a declaration has C linkage.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me