All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Tobler <a.tobler@schweiz.ch>
To: "linuxppc-dev@lists.linuxppc.org"
	<linuxppc-dev@lists.linuxppc.org>,
	egcs@egcs.cygnus.com
Subject: building egcs under LinuxPPC pre-R5
Date: Wed, 10 Feb 1999 09:34:40 +0100	[thread overview]
Message-ID: <36C144A0.A11501B1@schweiz.ch> (raw)


Hello,

since the beginning of February I try to build egcs snapshot 19990131
and now 19990208. The succcess is small. I got the 19990131 snapshot to
build and install, but when I compile c++ code with some include
restrictions it seems that it overrides it which causes an error. The
egcs I used before and now again, was 2.91.60 I think, for LinuxPPC
folks egcs-1.1.1.1c. With this compiler I haven't had this error.
My question, is there something specific when building an egcs on
LinuxPPC that I have to take care of? It's not necessary for me to take
a snapshot, but I need to build an egcs & libstdc++ with the option
-fno-vtable-thunks.

my config: 	LinuxPPC pre-R5 with glibc-2.0.108
		Kernel 2.2.0 self built
		running compiler egcs-1.1.1.1c
How I did egcs:	./configure --enable-shared --enable-threads
--prefix=/usr/local/egcs
		make LANGUAGES="c c++"
		make LANGUAGES="c c++" install
Any hints?
Thanks

Andreas
-- 
| Andreas Tobler				
| CH-8004 Zuerich 							
| E-Mail: andreas.tobler@alcatel.ch	| a.tobler@schweiz.ch
-----------------------------------------------------------

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

             reply	other threads:[~1999-02-10  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-10  8:34 Andreas Tobler [this message]
1999-02-10  9:40 ` building egcs under LinuxPPC pre-R5 Gary Thomas
1999-02-10 10:09   ` Andreas

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=36C144A0.A11501B1@schweiz.ch \
    --to=a.tobler@schweiz.ch \
    --cc=egcs@egcs.cygnus.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.