From: ian AT cygnus DOT com
Subject: Re: Bad linker behaviour
6 Oct 1997 10:44:50 -0700
Message-ID: <199710061729.NAA29946.cygnus.gnu-win32@tweedledumb.cygnus.com>
References: <199710061558 DOT QAA08198 AT zaphod DOT long DOT harlequin DOT co DOT uk>
To: jont AT harlequin DOT co DOT uk
Cc: gnu-win32 AT cygnus DOT com

>Ah well, it turns out that this is caused by C++ attempted name
>mangling, and only happens in the case where the symbols can't be
>matched (which is the case in my example above, although it wasn't
>meant to be). So, the end result is that for symbols which get name
>mangled like this, the error messages from ld are rubbish. Is there
>any way of getting ld to give the real error message, instead of the
>message after the name mangling?

No, I'm afraid ld always demangles symbol names in error messages.
The place to fix this is the function demangle in ld/ldmisc.c.

Ian
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".