Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ilya Volynets <ilya@theIlya.com>
To: linux-mips@oss.sgi.com
Subject: Toolchain patches
Date: Wed, 30 May 2001 09:14:43 -0700	[thread overview]
Message-ID: <01053009144307.01259@gateway> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey people.
As we all well know, toolchain is one of major issues for Linux/MIPS.
Probably the worst one. Personally I had just gone through getting it
at least semi-straight, and blood, sweat, tears, and peaces of raw flesh
are still lying arround. I don't think I'd like my enemies to go through this.
Now, one of the reasons for this is that maintainers of some important
tools (like gcc :-) are little bit too concentrated on Inhell architecture.
They do not apply our patches, they do not fix bugs reported by us,
and in general hurt our feelings :). Of course we could start maintaining our
own trees for respective tools, but unfortunately we simply do not have
manpower right now for that (and many people would give lots of other
good arguments against this). So, I decided to put together at least
a page with collection of patches to toolchain, that didn't go into tree
to make life at least a bit easier.
Send comments, patches, and anything else, you see appropriate to me.
I hope to get initial page up in couple of days.
	Ilya.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjsVHHoACgkQtKh84cA8u2k+rQCeLHzpSVBroqru0g95cyo5uJbB
askAnRmYdw28hSC06Sp/aYk1AbbTJzCX
=a6hH
-----END PGP SIGNATURE-----

             reply	other threads:[~2001-05-30 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 16:14 Ilya Volynets [this message]
2001-05-30 16:43 ` Toolchain patches Thiemo Seufer
2001-05-30 17:37   ` Ilya Volynets
2001-05-31 13:58     ` Ralf Baechle

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=01053009144307.01259@gateway \
    --to=ilya@theilya.com \
    --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