Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@pacbell.net>
To: "Sun, Lei" <lsun@3eti.com>
Cc: "'Zhang Fuxin'" <fxzhang@ict.ac.cn>, linux-mips@oss.sgi.com
Subject: Re: _gp_disp
Date: Wed, 12 Sep 2001 10:00:54 -0700	[thread overview]
Message-ID: <3B9F94C6.90300@pacbell.net> (raw)
In-Reply-To: 32CC5B62AF0BD2119E4C00A0C9663E226F8E29@MAIL

Sun, Lei wrote:
> Hi:
>   Unfortunately, make clean didn't work, the linking problem still sit
> there!

Do you have a binary image that you're trying to link, such as a ramdisk?

Pete

> 
> thanks
> lei 
> 
> -----Original Message-----
> From: Zhang Fuxin [mailto:fxzhang@ict.ac.cn]
> Sent: Wednesday, September 12, 2001 12:38 PM
> To: Sun, Lei
> Cc: linux-mips@oss.sgi.com
> Subject: Re: RE: _gp_disp
> 
> 
> Sun, Lei,您好!
> 
>  I think a make clean will do.
>  You got some .o lurking compiled without the flags
> 
> 在 2001-09-12 11:57:00 您写道:
> 
>>Thanks for the kind response.
>>after modified my Makefile according to Pete's suggestion, But I got the
>>following erro when linking
>>/opt/Embedix/tools/mipsel-linux/bin/ld: prism2dl.o: linking PIC files with
>>non-P
>>IC files
>>/opt/Embedix/tools/mipsel-linux/bin/ld: prism2dl.o: uses different e_flags
>>(0x100) fields than previous modules(0x0)
>>Bad value: failed to merge target specific data of file prism2dl.o
>>
>>ANy more input?
>>thank you!
>>lei 
>>
>>-----Original Message-----
>>From: Jun Sun [mailto:jsun@mvista.com]
>>Sent: Monday, September 10, 2001 7:18 PM
>>To: Pete Popov
>>Cc: Sun, Lei; Debian-Mips (E-mail)
>>Subject: Re: _gp_disp
>>
>>
>>Pete Popov wrote:
>>
>>>Sun, Lei wrote:
>>>
>>>>Hi:
>>>>  I was trying to port a wireless lan driver to MIPS based platform
>>>>
> (IDT
> 
>>>>79S334), the compilation seems fine, But when I try to load the created
>>>>module, it tells me "unresoved symbol _gp_disp".( I cross-compiled it
>>>>
> by
> 
>>>>mipsel-gcc compiler).
>>>>  By doing a quick grep in the driver source, I didn't find the gp_disp
>>>>symbol. My question is where did the _gp_disp come from and how I
>>>>
> should
> 
>>>>solve this problem?
>>>>
>>>>Appreciate your help!
>>>>
>>>You did not use the correct gcc options. Add these to your gcc flags and
>>>
>>it
>>
>>>should work (replace -mcpu=<cpu> if you need to):
>>>
>>>-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing
>>>
> -G
> 
>>0
>>
>>>-mno-abicalls -fno-pic -mcpu=r4600 -mips2 -Wa,--trap -pipe -DMODULE
>>>
>>-mlong-calls
>>
>>>   -DEXPORT_SYMTAB
>>>
>>>
>>I think some of the options might not be necessary, but you definitely need
>>"-DKERNEL"
>>
>>Jun
>>
>>
>>-- 
>>To UNSUBSCRIBE, email to debian-mips-request@lists.debian.org
>>with a subject of "unsubscribe". Trouble? Contact
>>
> listmaster@lists.debian.org
> 
>                     致
> 礼!
> 
>             Zhang Fuxin
>             fxzhang@ict.ac.cn
> 
> 

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

Thread overview: 4+ 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
2001-09-12 17:00 ` Pete Popov [this message]
2001-09-12 23:45 ` 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=3B9F94C6.90300@pacbell.net \
    --to=ppopov@pacbell.net \
    --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