This is the mail archive of the gcc-bugs@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]

Re: Unresolved references to __builtin functions building libgcj

To: Bryce McKinlay <bryce at albatross dot co dot nz>
Subject: Re: Unresolved references to __builtin functions building libgcj
From: Tom Tromey <tromey at cygnus dot com>
Date: 11 Oct 2000 20:21:26 -0600
Cc: gcc-bugs at gcc dot gnu dot org, java-discuss at sources dot redhat dot com
References: <39E3D43A.8DEA64A@albatross.co.nz> <or66mzi8b6.fsf@guarana.lsd.ic.unicamp.br> <39E51CD3.76CE69DF@albatross.co.nz>
Reply-To: tromey at cygnus dot com

>>>>> "Bryce" == Bryce McKinlay <bryce@albatross.co.nz> writes:

Bryce> Right. And for some reason libgcj isn't linked to libstdc++:

Bryce> It should be, right? So I added an explicit -lstdc++. Now I'm
Bryce> getting this:

Do we really want to do that?
Everything in libstdc++ except the low-level support bits is not
useful to libgcj.

Tom

Follow-Ups:
- Re: Unresolved references to __builtin functions building libgcj
  - From: Bryce McKinlay

References:
- Unresolved references to __builtin functions building libgcj
  - From: Bryce McKinlay
- Re: Unresolved references to __builtin functions building libgcj
  - From: Alexandre Oliva
- Re: Unresolved references to __builtin functions building libgcj
  - From: Bryce McKinlay

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