From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to compile oprofile when using an external binary toolchain
Date: Wed, 17 Mar 2010 13:16:06 +0100 [thread overview]
Message-ID: <20100317131606.07afc268@surf> (raw)
In-Reply-To: <570395.74949.qm@web24805.mail.ird.yahoo.com>
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
prev parent reply other threads:[~2010-03-17 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 13:07 [Buildroot] How to compile oprofile when using an external binary toolchain Gianluca
2010-03-17 11:50 ` [Buildroot] R: " Gianluca
2010-03-17 12:16 ` Thomas Petazzoni [this message]
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=20100317131606.07afc268@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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