From: Ilya Volynets <ilya@theIlya.com>
To: Arnaud Rolly <arolly@anfora.fr>, linux-mips@oss.sgi.com
Subject: Re: gcc 3.0 / glibc 2.2.3 cross-toolchain
Date: Thu, 9 Aug 2001 00:11:17 -0700 [thread overview]
Message-ID: <01080900111701.28762@gateway> (raw)
In-Reply-To: <01080909030303.06909@arnaud>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I offered something along these lines a while ago. I even started a little site.
Unfortunately I don't have enough time to keep up with current toolchain
patches, etc. myself, but if people send me patches, along with comments,
I'll post them at my site.
On Thursday 09 August 2001 06:03, Arnaud Rolly wrote:
> Le Mercredi 8 AoШt 2001 23:49, vous avez Иcrit :
> > I've chronicled my cross-toolchain mips-adventures at:
> >
> > http://www.ltc.com/~brad/mips/mipsel-linux-cross-toolchain-building.txt
> >
> > I included a copy of the glibc patch that has the MAP_BASE_ADDR fix in it
> > in the same directory, namely:
> >
> > http://www.ltc.com/~brad/mips/
> >
> > Regards,
> > Brad
>
> It would be great to have a patch repository, for example just a directory
> on the FTP of oss.sgi.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjtyN5kACgkQtKh84cA8u2lORwCcDr0csXgikuVFizIgBXJgncPv
zpQAoIGtXsSE7WMiBP0XODyWhEMhj9zb
=VJLD
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2001-08-09 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 23:42 gcc 3.0 / glibc 2.2.3 cross-toolchain Bradley D. LaRonde
2001-08-08 23:42 ` Bradley D. LaRonde
2001-08-08 23:45 ` Daniel Jacobowitz
2001-08-08 23:58 ` Bradley D. LaRonde
2001-08-08 23:58 ` Bradley D. LaRonde
2001-08-09 2:44 ` Bradley D. LaRonde
2001-08-09 2:44 ` Bradley D. LaRonde
2001-08-09 3:49 ` Bradley D. LaRonde
2001-08-09 3:49 ` Bradley D. LaRonde
2001-08-09 13:03 ` Arnaud Rolly
2001-08-09 7:11 ` Ilya Volynets [this message]
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=01080900111701.28762@gateway \
--to=ilya@theilya.com \
--cc=arolly@anfora.fr \
--cc=linux-mips@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox