Linking assembled PIC code with Linux libc library

Linking assembled PIC code with Linux libc library

[Sergio Ruiz]

Hi, i can't link assembled pic code against the libc running my
embedded-mips-box under debian, and this is what i do:

bluebox@bluebox:~$ as -al -EL -membedded-pic -mips1 -o prueba."o" prueba."s"

ld -L/usr/lib -lc -EL -o prueba prueba.o
ld: aviso: no se puede encontrar el símbolo de entrada __start; usando
por omisión 0000000000400280
prueba.o: En la función `main':
prueba.o(.text+0x8): relocation truncated to fit: R_MIPS_GNU_REL16_S2
printf@@GLIBC_2.0

I've been looking everywhere without any luck.
Any help is appreciated!
Thanks

Re: Linking assembled PIC code with Linux libc library

[Daniel Jacobowitz]

On Sat, Apr 09, 2005 at 02:09:14PM +0200, Sergio Ruiz wrote:
> Hi, i can't link assembled pic code against the libc running my
> embedded-mips-box under debian, and this is what i do:
> 
> bluebox@bluebox:~$ as -al -EL -membedded-pic -mips1 -o prueba."o" prueba."s"

PIC != embedded-pic.  You shouldn't be using -membedded-pic.

In fact, you shouldn't be using as directly, or ld.  Always use GCC to
assemble and link, and it will take care of the options for you.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: Linking assembled PIC code with Linux libc library

[Sergio Ruiz]

But if I use GCC with my assembler code, and I use a simple 'printf'
function, the assembler code I get is totally different than the
original one, so I cant debug it.

any other possibility?

thanks,

Sergio

Re: Linking assembled PIC code with Linux libc library

[Ralf Baechle]

On Sun, Apr 10, 2005 at 09:27:58PM +0200, Sergio Ruiz wrote:

> But if I use GCC with my assembler code, and I use a simple 'printf'
> function, the assembler code I get is totally different than the
> original one, so I cant debug it.

Sounds like you're being surprised by the gcc 3.4 optimization where gcc
may replace certain functions such as printf with a whole sequence of
calls to more basic stdio functions?

  Ralf