[Buildroot] How to compile oprofile when using an external binary toolchain

[Buildroot] How to compile oprofile when using an external binary toolchain

[Gianluca]

Hi all,

I'm trying to compile oprofile for a mipsel platform but I'm using an external binary toolchain and so when it tries to compile binutils it can't download the right binutils package because the version is not specified in .config.
I've tried to hack that by forcing the compilation of binutils 2.19.1 and it worked...but when I went finally to the last oprofile linking process I got some very strange linker errors like these:

non-dynamic relocations refer to dynamic symbol strcpy

and

failed to set dynamic section sizes: Bad value

Is there a "standard" way of compiling oprofile when using the external toolchain?
Thank you.

mrA



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100310/d712e032/attachment.htm>

[Buildroot] R: How to compile oprofile when using an external binary toolchain

[Gianluca]

Please, is there someone who could help me with this issue?
Thank you

mrA


--- Mer 10/3/10, Gianluca <funeral_party80@yahoo.it> ha scritto:

Da: Gianluca <funeral_party80@yahoo.it>
Oggetto: [Buildroot] How to compile oprofile when using an external binary toolchain
A: buildroot at busybox.net
Data: Mercoled? 10 marzo 2010, 14:07

Hi all,

I'm trying to compile oprofile for a mipsel platform but I'm using an external binary toolchain and so when it tries to compile binutils it can't download the right binutils package because the version is not specified in .config.
I've tried to hack that by forcing the compilation of binutils 2.19.1 and it worked...but when I went finally to the last oprofile linking process I got some very strange linker errors like these:

non-dynamic relocations refer to dynamic symbol strcpy

and

failed to set dynamic section sizes: Bad value

Is there a "standard" way of compiling oprofile when using the external toolchain?
Thank you.

mrA





      
-----Segue allegato-----

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100317/55891c4d/attachment.htm>

[Buildroot] How to compile oprofile when using an external binary toolchain

[Thomas Petazzoni]

On Wed, 10 Mar 2010 05:07:32 -0800 (PST)
Gianluca <funeral_party80@yahoo.it> wrote:

> I'm trying to compile oprofile for a mipsel platform but I'm using an
> external binary toolchain and so when it tries to compile binutils it
> can't download the right binutils package because the version is not
> specified in .config. I've tried to hack that by forcing the
> compilation of binutils 2.19.1 and it worked...but when I went
> finally to the last oprofile linking process I got some very strange
> linker errors like these:
> 
> non-dynamic relocations refer to dynamic symbol strcpy
> 
> and
> 
> failed to set dynamic section sizes: Bad value

I don't know about these, I would need to reproduce the problem.

> Is there a "standard" way of compiling oprofile when using the
> external toolchain? Thank you.

Peter, what do you think about this ?

For the moment, binutils for the target is compiled in
toolchain/binutils/binutils.mk, which isn't sourced when using an
external toolchain. Should we migrate the compilation of binutils for
the target to package/binutils (and use the Makefile.autotools.in
machinery) ? If so, how do we share the patches between
package/binutils and toolchain/binutils ? Should we still source
toolchain/binutils/binutils.mk even when an external toolchain is
selected ?

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com