From: Daniel Jacobowitz <dan@debian.org>
To: "Steven J. Hill" <sjhill@cotw.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Question on the binutils tradlittlemips patch
Date: Wed, 18 Apr 2001 16:37:27 -0400 [thread overview]
Message-ID: <20010418163727.A29531@nevyn.them.org> (raw)
In-Reply-To: <3ADDFD6A.AD0DDE4A@cotw.com>; from sjhill@cotw.com on Wed, Apr 18, 2001 at 03:47:38PM -0500
On Wed, Apr 18, 2001 at 03:47:38PM -0500, Steven J. Hill wrote:
> Daniel Jacobowitz wrote:
> >
> > I've been trying to make this patch work as part of a complete
> > toolchain, based on glibc. In addition to a little snag (when building
> > glibc for big-endian mips you need an equivalent change in the target
> > format), I hit a serious shared library error - nothing linked
> > dynamically worked. This is the cause:
> >
> Yes, I have a patch against GLIBC. Go to my FTP site here:
>
> ftp://ftp.cotw.com/pub/linux/nino/toolchain
>
> It is currently a hack as I have not figured out how to construct a
> patch for GLIBC since it will break the other MIPS targets. See if
> it helps.
If you're referring to libc-mips-04052001.patch.bz2, that's what I
started with. I needed two changes on top of it. I'll post them in a
bit.
--
Daniel Jacobowitz Debian GNU/Linux Developer
Monta Vista Software Debian Security Team
next prev parent reply other threads:[~2001-04-18 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 18:19 Question on the binutils tradlittlemips patch Daniel Jacobowitz
2001-04-18 20:11 ` Andreas Jaeger
2001-04-18 21:03 ` Daniel Jacobowitz
2001-04-18 20:47 ` Steven J. Hill
2001-04-18 20:37 ` Daniel Jacobowitz [this message]
2001-04-23 1:07 ` Keith M Wesolowski
2001-04-23 2:19 ` Daniel Jacobowitz
2001-04-23 4:23 ` Keith M Wesolowski
2001-04-23 4:34 ` Daniel Jacobowitz
2001-04-23 5:54 ` Andreas Jaeger
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=20010418163727.A29531@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@oss.sgi.com \
--cc=sjhill@cotw.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.