From: "Ringeman, Tim" <tim_ringeman@gilbarco.com>
Subject: x86 --> powerpc/MBX Cross Compiler
Date: Thu, 22 Jul 1999 14:46:32 -0400 [thread overview]
Message-ID: <199907221847.OAA29580@hoover.gilbarco.com> (raw)
Hi,
I was wondering if anyone has been able to get binaries for or build a C and
C++ x86 --> powerpc/MBX cross-compiler. I was able to get a C compiler a
while ago but now I need a C++ cross-compiler to be able to develop more
apps. Your help would be greatly appreciated.
Thanks,
Tim
Tim Ringeman
Gilbarco Inc.
Telephone 336-547-5946
e-mail: tim_ringeman@gilbarco.com
http://www.gilbarco.com
[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-07-22 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-22 18:46 Ringeman, Tim [this message]
1999-07-22 19:04 ` x86 --> powerpc/MBX Cross Compiler David Edelsohn
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=199907221847.OAA29580@hoover.gilbarco.com \
--to=tim_ringeman@gilbarco.com \
/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).