Date: Mon, 10 Mar 1997 15:31:08 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: current@freebsd.org Subject: Re: 2 questions about C++ support in 2.2 Message-ID: <199703102231.PAA23772@phaeton.artisoft.com> In-Reply-To: <24352.857903386@time.cdrom.com> from "Jordan K. Hubbard" at Mar 9, 97 02:29:46 am
next in thread | previous in thread | raw e-mail | index | archive | help
> /var/tmp/cc024167.s:10678: Warning: GOT relocation burb: `_Am_Standard_Widget_Abort_Method_proc__FG9Am_Object' should be global > > 1. What the hell is a "relocation burb" and how can one avoid them? :-) It means that there is a locally scoped item in the Global Offset Table used for relocation. It thinks the export and the declarative scoping conflict. How old is your assembler? It's probably the culprit... I defer to Warner for a better analysis... (ducks and runs). > 2. Shouldn't these messages demange the symbol first, so you don't > have to hassle with c++filt? I thought we were here once before > (though probably in connection with the loader) and everyone agreed > that built-in symbol demanging was good, very user friendly and > we should all do it. Whatever happened to that idea? :-) You'd have to demange it for attribution of paramters, since you could have a conflict declaration, and if you demanged it to not show any attribution of paramters or return value, you'd never figure out where the hell you screwed up. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703102231.PAA23772>