From: Maxim Osipov <maxim.osipov@gmail.com>
To: macro@linux-mips.org
Cc: linux-mips@linux-mips.org, dan@debian.org
Subject: Re: glibc-2.3.4 mips64 compilation failure
Date: Tue, 31 May 2005 20:30:35 +0400 [thread overview]
Message-ID: <6097c4905053109307edb80a6@mail.gmail.com> (raw)
In-Reply-To: <429C8F71.6080606@siemens.com>
Yes, thanks - I'm already using it, for glibc it did help with my
problem. Binutils 2.16 and gcc 3.4.3 seems to compile out of box (wo
any patches), but I didn't try produced code on a hardware yet.
Best regards,
Maxim
On 5/31/05, Maxim Osipov <maxim.osipov@siemens.com> wrote:
> > Do anyone have a clue what is happening? AFAIK, some people already
> > had success building glibc for mips64. Probably I miss something?
>
> Please feel free to have a look at packages available at my site -- the
> setup may seem a little bit odd (n64 is used as the default format and
> actually the only one supported), but if you are after general setup,
> patches, etc. it is still relevant; just ignore the odd stuff. Binary
> packages have been built with GCC 4.0.0, so probably the sources + patches
> are going to work with older tools as well. You may consider using
> binutils 2.16, though (in general, not to solve your particular problem).
>
> Maciej
>
next parent reply other threads:[~2005-05-31 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <429C8F71.6080606@siemens.com>
2005-05-31 16:30 ` Maxim Osipov [this message]
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
2005-05-26 20:33 ` Maciej W. Rozycki
2005-05-27 10:15 ` Maxim Osipov
2005-05-31 14:28 ` Maciej W. Rozycki
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=6097c4905053109307edb80a6@mail.gmail.com \
--to=maxim.osipov@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox