Linux-MIPS compilation

Linux-MIPS compilation

[Neeraj Garg, Noida]

Hi all,
I am trying to compile linux kernel version 2.4.19 and 2.4.20 for a MIPS
processor. GNU Compiler and linker version is 2.95.4.

-----------------
Compilation: 
------------------
Using compilation options:
mips-linux-gcc -D__KERNEL__ -D__linux__ -D_MIPS_SZLONG=32
-I/usr/emb_linux/linux-2.4.20/include -D__linux__ -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I
/usr/emb_linux/linux-2.4.20/include/asm/gcc -G 0 -mno-abicalls -fno-pic
-pipe -g -mcpu=r4600 -mips2 -Wa,--trap  -DUTS_MACHINE='"mips"'

I have got a tons of warnings named as:
{standard input}: Assembler messages:
{standard input}:784: Warning: Macro instruction expanded into multiple
instructions
{standard input}:784: Warning: No .cprestore pseudo-op used in PIC code

Can anybody help out to remove these warnings?

----------------------
Linking
-------------------
Using linking options:
mips-linux-ld -G 0 -static  -T arch/mips/ld.script

I have got a tons of error messages named as:
relocation truncated to fit: R_MIPS_PC16 cache_parity_error
relocation truncated to fit: R_MIPS_PC16 no symbol
relocation truncated to fit: R_MIPS_PC16 no symbol

I would be obliged if somebody can explain how GNU linker is taking
R_MIPS_PC16 as relocation type and what is the remedy to remove these error
messages?

Thanks and regds,
-neeraj


----------------------------------------------------------------------
Neeraj Kumar Garg            
Member Technical Staff

HCL Technologies Ltd.
A-5, Sector 24                Work: 91-11-91-2411502 Ext 2560
Noida UP - 201301             Fax:  91-11-91-2440155
India
----------------------------------------------------------------------

Re: Linux-MIPS compilation

[Ralf Baechle]

On Tue, Apr 01, 2003 at 12:05:18PM +0530, Neeraj  Garg, Noida wrote:

> Using compilation options:
> mips-linux-gcc -D__KERNEL__ -D__linux__ -D_MIPS_SZLONG=32
> -I/usr/emb_linux/linux-2.4.20/include -D__linux__ -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I
> /usr/emb_linux/linux-2.4.20/include/asm/gcc -G 0 -mno-abicalls -fno-pic
> -pipe -g -mcpu=r4600 -mips2 -Wa,--trap  -DUTS_MACHINE='"mips"'
> 
> I have got a tons of warnings named as:
> {standard input}: Assembler messages:
> {standard input}:784: Warning: Macro instruction expanded into multiple
> instructions
> {standard input}:784: Warning: No .cprestore pseudo-op used in PIC code
> 
> Can anybody help out to remove these warnings?

The options -D__linux__ -D_MIPS_SZLONG=32 and the error messages make it
look like you're forcing a non-Linux toolchain into building a kernel.

  Ralf

Re: Linux-MIPS compilation

[Brian Murphy]

Ralf Baechle wrote:

>The options -D__linux__ -D_MIPS_SZLONG=32 and the error messages make it
>look like you're forcing a non-Linux toolchain into building a kernel.
>
>  
>
What is the problem with this? At least a mips(el)-elf should have no 
problem compiling the kernel
(at least apart from the check you have somewhere which gives an error 
if you try).

/Brian

Re: Linux-MIPS compilation

[Ralf Baechle]

On Tue, Apr 01, 2003 at 03:57:19PM +0200, Brian Murphy wrote:

> >The options -D__linux__ -D_MIPS_SZLONG=32 and the error messages make it
> >look like you're forcing a non-Linux toolchain into building a kernel.
> >
> What is the problem with this? At least a mips(el)-elf should have no 
> problem compiling the kernel
> (at least apart from the check you have somewhere which gives an error 
> if you try).

These options are the default for every usable compiler.  If he actually
needed to add these options it looks like his compiler is pretty broken.
Similary the PIC-related error messages.  He's explicitly passing options
to disable PIC code yet the assembler and linker error messages indicate
he's using PIC code.  That's very strange also.

  Ralf

Re: Linux-MIPS compilation

[Geert Uytterhoeven]

On Tue, 1 Apr 2003, Brian Murphy wrote:
> Ralf Baechle wrote:
> >The options -D__linux__ -D_MIPS_SZLONG=32 and the error messages make it
> >look like you're forcing a non-Linux toolchain into building a kernel.
> >
> What is the problem with this? At least a mips(el)-elf should have no 
> problem compiling the kernel
> (at least apart from the check you have somewhere which gives an error 
> if you try).

Nope, I actually tried it yesterday with a 3.2.2. mips-elf-gcc I had lying
around from some other project, and it complained about the missing __linux__
and _MIPS_SZLONG.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: Linux-MIPS compilation

[Ralf Baechle]

On Tue, Apr 01, 2003 at 04:58:43PM +0200, Geert Uytterhoeven wrote:

> Nope, I actually tried it yesterday with a 3.2.2. mips-elf-gcc I had lying
> around from some other project, and it complained about the missing __linux__
> and _MIPS_SZLONG.

mips-elf is not mips-linux.

  Ralf