Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Andre.Messerschmidt@infineon.com, linux-mips@oss.sgi.com
Subject: Re: GCC and Modules
Date: Tue, 24 Jul 2001 09:30:56 -0700	[thread overview]
Message-ID: <20010724093056.A21216@lucon.org> (raw)
In-Reply-To: <20010724182057.D27225@bacchus.dhis.org>; from ralf@oss.sgi.com on Tue, Jul 24, 2001 at 06:20:57PM +0200

On Tue, Jul 24, 2001 at 06:20:57PM +0200, Ralf Baechle wrote:
> On Tue, Jul 24, 2001 at 08:40:05AM -0700, H . J . Lu wrote:
> 
> > > As I understand the current stable release of binutils and gcc is not able
> > > to compile functional modules. 
> > 
> > What are you talking about? My mips toolchain is as stable/good as the
> > x86 version for RedHat 7.1.
> 
> He's refering to the last official release of binutils which indeed wasn't
> usable for modutils.

What official release of binutils? Are we talking about the FSF
official release? Since when did Linux use those? They won't even
work right on Linux/x86. You should either use the Linux binutils
or try your luck with CVS.


H.J.

  reply	other threads:[~2001-07-24 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-24 11:14 GCC and Modules Andre.Messerschmidt
2001-07-24 15:40 ` H . J . Lu
2001-07-24 16:20   ` Ralf Baechle
2001-07-24 16:30     ` H . J . Lu [this message]
     [not found] <25369470B6F0D41194820002B328BDD27D2E@ATLOPS>
     [not found] ` <20010724085544.A20610@lucon.org>
     [not found]   ` <995995907.1331.5.camel@localhost.localdomain>
2001-07-24 20:25     ` H . J . Lu
2001-07-24 21:09       ` Marc Karasek
  -- strict thread matches above, loose matches on Subject: below --
2001-07-25  9:12 AW: " Andre.Messerschmidt
2001-07-25 11:24 ` 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=20010724093056.A21216@lucon.org \
    --to=hjl@lucon.org \
    --cc=Andre.Messerschmidt@infineon.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@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