Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: "Sun, Lei" <lsun@3eti.com>
Cc: "'Zhang Fuxin'" <fxzhang@ict.ac.cn>, linux-mips@oss.sgi.com
Subject: Re: RE: _gp_disp
Date: Wed, 12 Sep 2001 09:50:11 -0700	[thread overview]
Message-ID: <20010912095011.A4551@lucon.org> (raw)
In-Reply-To: <32CC5B62AF0BD2119E4C00A0C9663E226F8E29@MAIL>; from lsun@3eti.com on Wed, Sep 12, 2001 at 12:48:57PM -0400

On Wed, Sep 12, 2001 at 12:48:57PM -0400, Sun, Lei wrote:
> Hi:
>   Unfortunately, make clean didn't work, the linking problem still sit
> there!
> 

Please check the kernel source how to build the mips kernel modules.

# make modules

should give you a clue.


H.J.

  reply	other threads:[~2001-09-12 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-12 16:48 RE: _gp_disp Sun, Lei
2001-09-12 16:50 ` H . J . Lu [this message]
2001-09-12 17:00 ` _gp_disp Pete Popov
2001-09-12 23:45 ` _gp_disp Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2001-09-12 16:53 Sun, Lei
2001-09-12 16:57 ` H . J . Lu
2001-09-12 16:37 Zhang Fuxin

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=20010912095011.A4551@lucon.org \
    --to=hjl@lucon.org \
    --cc=fxzhang@ict.ac.cn \
    --cc=linux-mips@oss.sgi.com \
    --cc=lsun@3eti.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