From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: oprofile
Date: Fri, 25 Apr 2008 16:48:53 +1000 [thread overview]
Message-ID: <20080425064853.GA1525@cloud.net.au> (raw)
In-Reply-To: <87zlrj2khz.fsf@macbook.be.48ers.dk>
On Thu, Apr 24, 2008 at 08:08:56PM +0200, Peter Korsgaard wrote:
> >>>>> "ninevoltz" == ninevoltz <ninevoltz@uclibc.org> writes:
>
> ninevoltz> Author: ninevoltz
> ninevoltz> Date: 2008-04-24 09:54:29 -0700 (Thu, 24 Apr 2008)
> ninevoltz> New Revision: 21847
>
> ninevoltz> Log:
> ninevoltz> add oprofile
>
> ninevoltz> Added:
> ninevoltz> trunk/buildroot/package/oprofile/
> ninevoltz> trunk/buildroot/package/oprofile/Config.in
> ninevoltz> trunk/buildroot/package/oprofile/oprofile-0.9.3-avr32.patch
>
> Please use the .patch.avr32 naming convention.
Isn't that only required if the patch is arch-specific, ie it breaks
other architectures? A quick look at the patch suggests to me that it
adds avr32 support to profile without breaking anything else. Ie it's
safe to always apply it.
> Does that actually work? I mean, does the compiler get recompiled with
> C++ support if you select this package after your initial make?
I doubt it.. I think it's quite difficult to get gcc recompiled after
changing the options - usually means deleting most (if not all) of
toolchain_build_$arch.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-04-25 6:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 16:54 [Buildroot] svn commit: trunk/buildroot/package: oprofile ninevoltz at uclibc.org
2008-04-24 18:08 ` Peter Korsgaard
2008-04-24 18:20 ` John Voltz
2008-04-24 18:46 ` Peter Korsgaard
2008-04-24 19:04 ` John Voltz
2008-04-25 8:17 ` Hans-Christian Egtvedt
2008-04-25 6:48 ` Hamish Moffatt [this message]
2008-04-25 8:09 ` Bernhard Fischer
2008-04-25 8:18 ` Peter Korsgaard
2008-04-25 8:36 ` Bernhard Fischer
2008-04-25 8:21 ` 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=20080425064853.GA1525@cloud.net.au \
--to=hamish@cloud.net.au \
--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