From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: mohanlal jangir <mohanlaljangir@hotmail.com>, linux-mips@linux-mips.org
Subject: Re: NPTL info needed
Date: Mon, 22 Aug 2005 11:59:15 -0500 [thread overview]
Message-ID: <430A0463.4070004@realitydiluted.com> (raw)
In-Reply-To: <20050821200151.GA23815@taniwha.stupidest.org>
Chris Wedgwood wrote:
>
> How stable is GCC is head? Hostorically thre have been periods of
> time when gcc itself wasn't stable or the code it produce wasn't
> stable.
>
The last working GCC 4.1.0 I checked out was on 20050604. I have yet
to get a cross build to work with uClibc. glibc-based toolchains seem
to work okay, but yes, GCC 4.1.0 is a piece of ****.
-Steve
prev parent reply other threads:[~2005-08-22 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 11:11 NPTL info needed mohanlal jangir
2005-08-18 11:11 ` mohanlal jangir
2005-08-18 18:04 ` Ton Truong
2005-08-18 18:22 ` mlachwani
2005-08-19 14:02 ` mohanlal jangir
2005-08-19 14:02 ` mohanlal jangir
2005-08-21 19:34 ` Steven J. Hill
2005-08-21 20:01 ` Chris Wedgwood
2005-08-22 16:59 ` Steven J. Hill [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=430A0463.4070004@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=cw@f00f.org \
--cc=linux-mips@linux-mips.org \
--cc=mohanlaljangir@hotmail.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