This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: re[2]: alpha-dec-osf5.0 Can't compile libstdc++-v3/libsupc++/pure.cc
- To: Greg Freemyer <freemyer at NorcrossGroup dot com>
- Subject: Re: re[2]: alpha-dec-osf5.0 Can't compile libstdc++-v3/libsupc++/pure.cc
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Tue, 27 Feb 2001 09:26:28 -0800 (PST)
- cc: GCC Mailing List <libstdc++ at gcc dot gnu dot org>
> Thanks for the attempt, but I am still having problems.
Oh well. It was worth a try.
> This starting to look like a C++ 3.0 problem to me, not a libstdc++ problem, so let me know if I need to ask for help in different mailing list. In particular, I suspect one or more of the 'fixed' include files is incorrect.
Yeah gcc-bugs cc'd to the fixinclude guy is probably the best bet.
> /usr/local/src/gcc.devel/gcc/objdir-gcc/gcc/g++ -B/usr/local/src/gcc.devel/gcc/objdir-gcc/gcc/ -nostdinc++ -L/usr/local/src/gcc.devel/gcc/objdir-gcc/alpha-dec-osf5.0/libstdc++-v3/src -L/usr/local/src/gcc.devel/gcc/objdir-gcc/alpha-dec-osf5.0/libstdc++-v3/src/.libs -B/usr/local/alpha-dec-osf5.0/bin/ -B/usr/local/alpha-dec-osf5.0/lib/ -isystem /usr/local/alpha-dec-osf5.0/include -I../../../../libstdc++-v3/../gcc -I../../../../libstdc++-v3/../include -I../../../../libstdc++-v3/include -I../../../../libstdc++-v3/include/std -I../../../../libstdc++-v3/include/c_std -I../include -I../../../../libstdc++-v3/libsupc++ -g -O2 -mieee -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -g -c ./../../../libstdc++-v3/libsupc++/pure.cc -DPIC -o pure.o
>
> /usr/local/src/gcc.devel/gcc/objdir-gcc/gcc/include/stdio.h: In function `void
> __cxa_pure_virtual()':
>
> /usr/local/src/gcc.devel/gcc/objdir-gcc/gcc/include/stdio.h:245: too many
> arguments to function `int fputs()'
it looks like the declarations are wrong too...
> I admit to being a little rusty on my C++, so I'm not clear as to what
> the problem is, but note that the 'extern "C" {' occurs twice, but is
> only terminated once.
... a problm..
> Could that somehow be the culprit, and if so, is the problem likely in
> the fixed types.h file?
yep. Try manually editing it and seeing if it solved the problem, or gets
you farther along...