Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca <funeral_party80@yahoo.it>
To: buildroot@busybox.net
Subject: [Buildroot] R: How to compile oprofile when using an external binary toolchain
Date: Wed, 17 Mar 2010 04:50:35 -0700 (PDT)	[thread overview]
Message-ID: <635340.71959.qm@web24812.mail.ird.yahoo.com> (raw)
In-Reply-To: <570395.74949.qm@web24805.mail.ird.yahoo.com>

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>

  reply	other threads:[~2010-03-17 11:50 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 ` Gianluca [this message]
2010-03-17 12:16 ` Thomas Petazzoni

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=635340.71959.qm@web24812.mail.ird.yahoo.com \
    --to=funeral_party80@yahoo.it \
    --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