From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot find libbfd library in compiled toolchain
Date: Mon, 30 Mar 2009 09:45:53 +0200 [thread overview]
Message-ID: <87skkvbgi6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <B3B0FE219DFDB64F8905B1567ECB01BC8B40B1@urano.tmt.telital.com> (Daniele Palmas's message of "Mon\, 30 Mar 2009 09\:18\:34 +0200")
>>>>> "Daniele" == Daniele Palmas <Daniele.Palmas@telit.com> writes:
Hi,
I'ce CC'ed the buildroot list again. Please keep buildroot
communication on the list.
Daniele> Thanks for your answer.
Daniele> Unfortunately I really mean 20080312: we have a product
Daniele> based on this version of buildroot (and on the resulting
Daniele> toolchain) and, for several reason, we cannot change this.
Ohh, that makes it harder to support you, but I'll try anyway.
Daniele> I need libbfd because I want to build oprofile: it is one of
Daniele> the requirements that should be fulfilled for
Daniele> cross-compiling it. I've chosen oprofile because I've read
Daniele> that gprof (one of the most common profiling tool for Linux)
Daniele> doesn't work with uclibc.
I've never used either oprofile or gprof on uclibc, so I wouldn't
know.
You are aware that we have an oprofile package in buildroot these
days? It got added almost a year ago:
Author: Ninevoltz <ninevoltz@uclibc.org>
Date: Thu Apr 24 16:54:29 2008 +0000
add oprofile
git-svn-id: svn+ssh://uclibc.org/svn/trunk/buildroot at 21847
You could try backporting that to your version.
--
Bye, Peter Korsgaard
next parent reply other threads:[~2009-03-30 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B3B0FE219DFDB64F8905B1567ECB01BC8B40B1@urano.tmt.telital.com>
2009-03-30 7:45 ` Peter Korsgaard [this message]
2009-03-30 8:18 ` [Buildroot] Cannot find libbfd library in compiled toolchain Daniele Palmas
2009-03-27 8:22 Daniele Palmas
2009-03-29 21:26 ` Peter Korsgaard
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=87skkvbgi6.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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