From: Jim Gifford <maillist@jg555.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Christoph Hellwig <hch@lst.de>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: Building o32 glibc on mips64
Date: Tue, 14 Jun 2005 01:00:05 -0700 [thread overview]
Message-ID: <42AE8E85.4080708@jg555.com> (raw)
In-Reply-To: <20050613205558.GA26829@nevyn.them.org>
From my understanding it's only supported when using IRIX shared
libraries, but the standard MIPS64 still only builds n32 and n64 only,
and not the o32 libraries.
I don't see why GCC didn't just allow all MIPS have that capability.
--
----
Jim Gifford
maillist@jg555.com
next prev parent reply other threads:[~2005-06-14 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 18:54 Building o32 glibc on mips64 Jim Gifford
2005-06-13 19:56 ` Daniel Jacobowitz
2005-06-13 20:05 ` Maciej W. Rozycki
2005-06-13 20:08 ` Christoph Hellwig
2005-06-13 20:18 ` Maciej W. Rozycki
2005-06-13 20:55 ` Daniel Jacobowitz
2005-06-14 8:00 ` Jim Gifford [this message]
2005-06-14 10:36 ` Richard Sandiford
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=42AE8E85.4080708@jg555.com \
--to=maillist@jg555.com \
--cc=dan@debian.org \
--cc=hch@lst.de \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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