HELP w/bug on.... mangling? new-api? something else?

Chip Salzenberg
Sun Jun 11 17:31:00 GMT 2000

According to Martin v. Loewis:
> I can't answer your question, so you may either want to investigate it
> yourself, or produce a bug report (preprocessor output etc).

Good suggestion.  Here is the full (yet still confusing) bug report.

The attached preprocessor source, when compiled by 'cc1plus
-fnew-abi', results in references to the following symbols, which end
up as unresolved external refs in the libstdc++-v3 shared library:


Here's the full command line:

    cc1plus strstream.i -quiet -dumpbase -g -g -O2 -Wall -Wno-format -W -Wwrite-strings -Winline -Werror -version -fnew-abi -fvtable-thunks -fno-implicit-templates -fdiagnostics-show-location=once -fPIC -o strstream.s

And here's my gcc configuration:

    configure --with-gcc-version-trigger=/u/build/gcc/egcs/SRC/gcc/version.c --host=i686-pc-linux --prefix=/usr/local/egcs --enable-threads=posix --enable-shared --enable-version-specific-runtime-libs --enable-languages=objc,c++ --enable-new-gxx-abi --enable-namespaces --enable-libstdcxx-v3 --enable-long-long --norecursion 

Chip Salzenberg              - a.k.a. -              <>
"I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early."  // MST3K
-------------- next part --------------
A non-text attachment was scrubbed...
Name: strstream.i.gz
Type: application/x-gzip
Size: 51868 bytes
Desc: not available
URL: <>

More information about the Gcc-bugs mailing list