All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alistair Lambie" <alambie@wellington.sgi.com>
To: linux@cthulhu.engr.sgi.com
Subject: (Fwd) Re: SGI/MIPS Linux port status
Date: Tue, 2 Jul 1996 10:13:22 +0000	[thread overview]
Message-ID: <9607021013.ZM1444@windy.wellington.sgi.com> (raw)

Folks,

I ping'ed Ralf about shared GNU libc for big endian machines.  At the end of
his reply he asks for some info to help him.  I'm not sure if he is on the
list of blessed people or not, and I suspect there are some others who would
be far more able to answer his question than myself.

Can someone follow this up.....(Ariel, Larry, Bill ???)

Cheers, Alistair

--- Forwarded mail from Ralf Baechle <ralf@Julia.DE>

From: Ralf Baechle <ralf@Julia.DE>
Subject: Re: SGI/MIPS Linux port status
To: alambie@wellington.sgi.com (Alistair Lambie)
Date: Mon, 1 Jul 1996 23:54:00 +0200 (MET DST)

Hi,

> > The even better news is that I've started to rebuild my entire system
> > using ELF shared libraries.  I'll try to make first alpha release of
> > shared library binaries tomorrow for little endian binaries (the above
> > mentioned machines are all little endian); I'll try to generate big
> > endian libs as soon as possible.
> >
> I have been building up a core set of binaries for us to use on the SGI
boxes.
> These are of course big endian, and naturally HUGE because they are
statically
> linked!

I know how big your binaries are - after all I'm still using a mostly
static linked system also.  So I assume that your /bin/ls is also about
15 times the size of the i486-linux shared /bin/ls ...

           Can you let me know when you have big endian shared libs so I can
have
> something a little more sane to deal with.

I'm rebulding my entire toolchain for big endian.  This night I should find
the time to rebuild the libs, also.

> BTW, I assume that you are using GNU libc?

Yes, I'm using GNU libc snapshot 960619.  Linux libc is lacking tons of code
required for MIPS fp support.  The problem is simply that MIPS only has the
capabilities to add, subtract, multiply and divide in hardware, some FPUs
can do sqrt() while Intel/68881/68882 can do many complex computations in
hardware.  Also HJ's way to maintain the code and the code itself made it
a bit of a pain to use Linux libc ...

On which libc is your SGI stuff based?  Also I'm trying to make my work
as SGI-ish as possible.  I don't have access to a SGI or documentation but
have some questions about IRIX regarding the shared lib stuff, PIC code
and more.  Can you help me?

Happy hacking,

  Ralf


---End of forwarded mail from Ralf Baechle <ralf@Julia.DE>

-- 
Alistair Lambie					    alambie@wellington.sgi.com
Silicon Graphics New Zealand				  SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower,				    Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ			  	   Fax: +64-4-802 1459

                 reply	other threads:[~1996-07-01 22:13 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=9607021013.ZM1444@windy.wellington.sgi.com \
    --to=alambie@wellington.sgi.com \
    --cc=linux@cthulhu.engr.sgi.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 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.