From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] oprofile build error related to gcc
Date: Thu, 18 Sep 2008 09:01:04 +0200 [thread overview]
Message-ID: <20080918090104.0de32924@atmel.com> (raw)
In-Reply-To: <87k5dav9kg.fsf@macbook.be.48ers.dk>
On Wed, 17 Sep 2008 21:47:27 +0200
Peter Korsgaard <jacmet@uclibc.org> wrote:
> >>>>> "J" == J Lee <jameslee05@gmail.com> writes:
>
> J> I got this error while I was building oprofile for a powerpc
> J> target. I have checked gcc directories but I did not see any
> J> gcc_s_nof. How can I get around this?
>
> I don't know right away, but oprofile got updated this morning to 0.94
> - Could you give that a try?
>
Hopefully 0.9.4 will work, the test case was to compile on AVR32 and
PowerPC, and they passed.
The previous oprofile in Buildroot was pretty broken and would probably
not work for anybody.
--
Best regards,
Hans-Christian Egtvedt
prev parent reply other threads:[~2008-09-18 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 18:38 [Buildroot] oprofile build error related to gcc J Lee
2008-09-17 19:47 ` Peter Korsgaard
2008-09-18 7:01 ` Hans-Christian Egtvedt [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=20080918090104.0de32924@atmel.com \
--to=hans-christian.egtvedt@atmel.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