From: "David S. Miller" <davem@jenolan.rutgers.edu>
To: shaver@neon.ingenia.ca
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: all in the family
Date: Wed, 9 Apr 1997 22:26:18 -0400 [thread overview]
Message-ID: <199704100226.WAA01960@jenolan.caipgeneral> (raw)
In-Reply-To: <199704100211.WAA16857@neon.ingenia.ca> (message from Mike Shaver on Wed, 9 Apr 1997 22:11:01 -0400 (EDT))
From: Mike Shaver <shaver@neon.ingenia.ca>
Date: Wed, 9 Apr 1997 22:11:01 -0400 (EDT)
Looks like I may be getting a machine here to see if we can migrate
some of our non-Oracle machines to Linux/SPARC.
Anyone know if the emulation is up to hosting the Linux/Indy
cross-compiler?
It should be straight forward, 32-bit to 32-bit crosses under gcc work
flawlessly right out of the box for everything I've ever tried. It's
when you cross from 32-bit to 64-bit that you may hit a bug or two.
In related news, we'll then have Linux running on 5 architectures
in the same room (Intel, Alpha, SPARC, ELKS, Indy). Maybe I'll
steal the PowerMac too... =)
ELKS, that is cheating ;-)
---------------------------------------------////
Yow! 11.26 MB/s remote host TCP bandwidth & ////
199 usec remote TCP latency over 100Mb/s ////
ethernet. Beat that! ////
-----------------------------------------////__________ o
David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><
next prev parent reply other threads:[~1997-04-10 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-10 2:11 all in the family Mike Shaver
1997-04-10 2:26 ` David S. Miller [this message]
1997-04-10 7:01 ` Ralf Baechle
1997-04-10 7:01 ` Ralf Baechle
1997-04-10 15:09 ` Mike Shaver
1997-04-10 15:09 ` Mike Shaver
1997-04-10 7:18 ` Miguel de Icaza
1997-04-10 14:53 ` Mike Shaver
1997-04-10 14:53 ` Mike Shaver
1997-04-10 14:22 ` Ralf Baechle
1997-04-10 14:22 ` Ralf Baechle
1997-04-10 15:30 ` Mike Shaver
1997-04-10 15:30 ` Mike Shaver
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=199704100226.WAA01960@jenolan.caipgeneral \
--to=davem@jenolan.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
--cc=shaver@neon.ingenia.ca \
/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.