If you are building your module as part of kernel (make modules) that should take care of the flags.
You might be seeing a binutil issue. I think loadable modules were broken until the trad[big|little]mips emulations. What version of binutils are you using? Regards, Brad ----- Original Message ----- From: "Sun, Lei" <[EMAIL PROTECTED]> To: "'Pete Popov'" <[EMAIL PROTECTED]>; "Jun Sun" <[EMAIL PROTECTED]> Cc: "Sun, Lei" <[EMAIL PROTECTED]>; "Debian-Mips (E-mail)" <[email protected]> Sent: Tuesday, September 11, 2001 11:19 AM Subject: RE: _gp_disp > Could you tell me which options will cause the "_gp_disp" disappear? I > assume some options are CPPFLAGS such as -DMODULE > and -DEXPORT_SYMTAB. My platform is RC32334 processor from IDT system, what > mcpu option should I choose for this? > > Thank you! > regards > lei sun > > -----Original Message----- > From: Pete Popov [mailto:[EMAIL PROTECTED] > Sent: Monday, September 10, 2001 7:32 PM > To: Jun Sun > Cc: Sun, Lei; Debian-Mips (E-mail) > Subject: Re: _gp_disp > > > Jun Sun wrote: > > 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" > > Probably not all the options are necessary, but this is safe. These are the > same > options the Makefiles in the kernel use. > > Pete > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
