From: Daniel Jacobowitz <dan@debian.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: maxim@mox.ru, linux-mips@linux-mips.org
Subject: Re: glibc-2.3.4 mips64 compilation failure
Date: Thu, 26 May 2005 16:24:15 -0400 [thread overview]
Message-ID: <20050526202415.GA19298@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61L.0505262118310.29423@blysk.ds.pg.gda.pl>
On Thu, May 26, 2005 at 09:22:47PM +0100, Maciej W. Rozycki wrote:
> On Thu, 26 May 2005, Daniel Jacobowitz wrote:
>
> > > It's buried in:
> > > http://sourceware.org/ml/libc-alpha/2004-12/msg00063.html
> >
> > ... not that those will be very useful to you, unless you want to
> > suddenly become Fedora. They'll only be useful to Debian once in a
> > blue moon.
>
> Thanks for the link and indeed -- I don't think we have any setup
> available that would qualify as a "distribution" as referred to by the
> rules. Especially as for MIPS you'd have to multiply that by three for
> the supported ABIs.
>
> As a result we have no glibc release that would work for a reasonably
> modern setup of MIPS/Linux.
HEAD does work, however. I will even get around to the MIPS64 NPTL
bits for HEAD very soon.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-26 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 16:32 glibc-2.3.4 mips64 compilation failure Maxim Osipov
2005-05-26 17:06 ` Daniel Jacobowitz
2005-05-26 17:26 ` Maciej W. Rozycki
2005-05-26 19:05 ` Daniel Jacobowitz
2005-05-26 19:34 ` Maciej W. Rozycki
2005-05-26 20:08 ` Daniel Jacobowitz
2005-05-26 20:15 ` Daniel Jacobowitz
2005-05-26 20:22 ` Maciej W. Rozycki
2005-05-26 20:24 ` Daniel Jacobowitz [this message]
2005-05-26 20:33 ` Maciej W. Rozycki
2005-05-27 10:15 ` Maxim Osipov
2005-05-31 14:28 ` Maciej W. Rozycki
[not found] <429C8F71.6080606@siemens.com>
2005-05-31 16:30 ` Maxim Osipov
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=20050526202415.GA19298@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=maxim@mox.ru \
/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.