From: David Daney <ddaney@avtrex.com>
To: "Ratin Rahman (mratin)" <mratin@cisco.com>
Cc: linux-mips@linux-mips.org
Subject: Re: upgrading glibc for mipsel
Date: Thu, 28 Jun 2007 19:03:10 -0700 [thread overview]
Message-ID: <4684685E.4090805@avtrex.com> (raw)
In-Reply-To: <27801B4D04E7CA45825B0E0CE60FE10A01F971CF@xmb-sjc-237.amer.cisco.com>
Ratin Rahman (mratin) wrote:
> In an effort to build gdbserver, I am trying to upgrade my glibc and
> gcc cross compile tools. I am having
> problem while bulding glibc-2.3.3, mipsel compiler version 3.2.3 and
> current glibc ver
> is 2.2.5.
>
Stock glibc-2.3.3 will not work on mipsel-linux. I posted the patch I
use few years ago to this list. You could try with that patch. Or look
at the cross-tool project. Some people have had success using it to
build toolchains.
David Daney
next prev parent reply other threads:[~2007-06-29 2:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 16:14 [PATCH] generic clk API implementation for MIPS Atsushi Nemoto
2007-06-26 9:37 ` Franck Bui-Huu
2007-06-26 14:33 ` Atsushi Nemoto
2007-06-26 15:20 ` Franck Bui-Huu
2007-06-26 16:33 ` Atsushi Nemoto
2007-06-26 20:02 ` Franck Bui-Huu
2007-06-27 7:51 ` Atsushi Nemoto
2007-06-27 15:39 ` Christoph Hellwig
2007-06-28 2:22 ` Atsushi Nemoto
2007-06-28 8:37 ` Christoph Hellwig
2007-06-28 9:26 ` Atsushi Nemoto
2007-06-28 20:45 ` gdbserver Ratin Rahman (mratin)
2007-06-28 20:45 ` gdbserver Ratin Rahman (mratin)
2007-06-28 21:41 ` gdbserver David Daney
2007-06-28 22:19 ` gdbserver Ratin Rahman (mratin)
2007-06-28 22:19 ` gdbserver Ratin Rahman (mratin)
2007-06-29 1:26 ` upgrading glibc for mipsel Ratin Rahman (mratin)
2007-06-29 1:26 ` Ratin Rahman (mratin)
2007-06-29 2:03 ` David Daney [this message]
2007-06-29 2:26 ` Jason Talley
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=4684685E.4090805@avtrex.com \
--to=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=mratin@cisco.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.