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: collect2 / ld giving strange errors with undefined virtual functions

To: oliva at dcc dot unicamp dot br
Subject: Re: collect2 / ld giving strange errors with undefined virtual functions
From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
Date: Mon, 29 Mar 1999 08:03:43 +0200
CC: smilodon at niksula dot hut dot fi, egcs-bugs at egcs dot cygnus dot com
References: <Pine.LNX.3.95.990326023645.5280A-100000@jt7-234.tky.hut.fi> <orsoat82zp.fsf@dcc.unicamp.br> <199903260841.JAA01745@mira.isdn.cs.tu-berlin.de> <or677l5i70.fsf@araguaia.dcc.unicamp.br>

> I'm not sure how the linker could figure out what is the method whose
> definition is missing.  Only if the vt mangling included the name of
> such method, which we could introduce in the new ABI.

That could be similar to the linker warning. If there is a section
.gnu.warning.SYMBOL, linking SYMBOL will result in printing the
message with the name __evoke_link_warning_SYMBOL.

Regards,
Martin

References:
- collect2 / ld giving strange errors with undefined virtual functions
  - From: Smilodon
- Re: collect2 / ld giving strange errors with undefined virtual functions
  - From: Alexandre Oliva
- Re: collect2 / ld giving strange errors with undefined virtual functions
  - From: Alexandre Oliva

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