From: Johannes Stezenbach <js@convergence.de>
To: Florian Lohoff <flo@rfc822.org>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@oss.sgi.com
Subject: Re: gcc include strangeness
Date: Mon, 11 Feb 2002 17:53:25 +0100 [thread overview]
Message-ID: <20020211165325.GB3261@convergence.de> (raw)
In-Reply-To: <20020211153732.GA31248@paradigm.rfc822.org>
On Mon, Feb 11, 2002 at 04:37:32PM +0100, Florian Lohoff wrote:
> On Mon, Feb 11, 2002 at 03:27:08PM +0100, Johannes Stezenbach wrote:
> >
> > The glibc-2.2.5/FAQ says:
> > 1.20. Which tools should I use for MIPS?
> >
> > {AJ} You should use the current development version of gcc 3.0 or newer from
> > CVS. gcc 2.95.x does not work correctly on mips-linux.
> >
>
> Its not about gcc development but rather keeping a distribution in
> sync. All Debian archs try to use the same compiler which is currently
> 2.95.4 which we are happy with right now - Except some minor issues
> breaking 2-3 Packages ...
So does this mean that Debian's gcc 2.95.4 works on MIPS?
Does it include patches which are not in CVS (gcc-2_95-branch)?
Regards,
Johannes
next prev parent reply other threads:[~2002-02-11 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 15:01 gcc include strangeness Florian Lohoff
2002-02-10 11:11 ` Ralf Baechle
2002-02-12 11:49 ` Maciej W. Rozycki
2002-02-11 12:51 ` Maciej W. Rozycki
2002-02-11 13:53 ` Florian Lohoff
2002-02-11 14:15 ` Maciej W. Rozycki
2002-02-11 14:27 ` Johannes Stezenbach
2002-02-11 15:10 ` Maciej W. Rozycki
2002-02-11 16:28 ` Johannes Stezenbach
2002-02-11 17:06 ` Maciej W. Rozycki
2002-02-11 22:20 ` Ralf Baechle
2002-02-12 15:55 ` Dominic Sweetman
2002-02-12 15:55 ` Dominic Sweetman
2002-02-12 17:08 ` Brian Murphy
2002-02-12 17:20 ` Timothy Daly
2002-02-11 22:07 ` Ralf Baechle
2002-02-11 22:07 ` Ralf Baechle
2002-02-11 15:37 ` Florian Lohoff
2002-02-11 16:53 ` Johannes Stezenbach [this message]
2002-02-11 17:08 ` Guido Guenther
2002-02-11 22:04 ` 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=20020211165325.GB3261@convergence.de \
--to=js@convergence.de \
--cc=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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