linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: ian reinhart geiser <geiseri@msoe.edu>
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: OLD gcc source needed...
Date: Sun, 17 Oct 1999 13:27:32 -0400	[thread overview]
Message-ID: <9910171727.AA10306@marc.watson.ibm.com> (raw)
In-Reply-To: Message from ian reinhart geiser <geiseri@msoe.edu> of "Sun, 17 Oct 1999 12:28:10 CDT." <Pine.LNX.4.10.9910171226120.1006-100000@sleepchamber.apt5.msoe.edu>


	gcc-2.6.3 did not support Linux/PPC.  It may not have supported
SVR4/ELF PowerPC ABI used by Linux/PPC at all.

David

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-10-17 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-17 17:28 OLD gcc source needed ian reinhart geiser
1999-10-17 17:27 ` David Edelsohn [this message]
1999-10-17 17:45   ` ian reinhart geiser
1999-10-17 21:32   ` Michael Meissner

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=9910171727.AA10306@marc.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=geiseri@msoe.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@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).