From: Andreas Tobler <toa@pop.agri.ch>
To: LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Libg++2.8.x build
Date: Sat, 20 Feb 1999 00:01:48 +0100 [thread overview]
Message-ID: <36CDED59.65562A34@pop.agri.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
Hello,
I know you are further than me and you are working at least with > egcs 1.0.2
and > libg++. But I can't, due to the vtable bug. So I try to build libg++
2.8.0.1. But I got the following errors:
See Attachment.
Does anybody of you have an idea where to setup the work? I think it should be
possible to bring this to work since I have dl/d the source as rpm. So I
suppose there was a least a person before who did that.
Two words to my config: kernel 2.2.0; glibc 2.0.108 >> pre R5!!
Thanks for any hints
Andreas
--
------------------
| Andreas Tobler
| CH-8004 Zuerich
| E-mail: toa@pop.agri.ch
------------------------------------------
[-- Attachment #2: BBEdit Lite 4.0 Document --]
[-- Type: text/plain, Size: 1641 bytes --]
make[1]: Entering directory `/usr/src/redhat/BUILD/libg++/libraries/libio'
test -z "-fPIC" || \
c++ -c -O2 -fsigned-char -fno-implicit-templates -I. -I. -nostdinc++ -D_IO_MTSAFE_IO -fPIC builtinbuf.cc -o pic/builtinbuf.o
In file included from streambuf.h:36,
from builtinbuf.h:32,
from builtinbuf.cc:29:
libio.h:270: invalid exception specifications
libio.h:271: invalid exception specifications
libio.h:272: invalid exception specifications
libio.h:273: invalid exception specifications
In file included from iostreamP.h:26,
from builtinbuf.cc:30:
libioP.h:94: invalid exception specifications
libioP.h:100: invalid exception specifications
libioP.h:107: invalid exception specifications
libioP.h:119: invalid exception specifications
libioP.h:126: invalid exception specifications
libioP.h:133: invalid exception specifications
libioP.h:143: invalid exception specifications
libioP.h:156: invalid exception specifications
libioP.h:164: invalid exception specifications
libioP.h:170: invalid exception specifications
libioP.h:176: invalid exception specifications
libioP.h:194: invalid exception specifications
libioP.h:201: invalid exception specifications
libioP.h:209: invalid exception specifications
libioP.h:219: invalid exception specifications
libioP.h:226: invalid exception specifications
libioP.h:233: invalid exception specifications
libioP.h:238: invalid exception specifications
libioP.h:453: invalid exception specifications
make[1]: *** [builtinbuf.o] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/libg++/libraries/libio'
make: *** [all-target-libio] Error 2
reply other threads:[~1999-02-19 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36CDED59.65562A34@pop.agri.ch \
--to=toa@pop.agri.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).