From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sysprof: New package.
Date: Tue, 31 Jul 2012 11:04:20 +0200 [thread overview]
Message-ID: <20120731110420.76490dd1@skate> (raw)
In-Reply-To: <20120730235830.27770869@skate>
Hello Will,
Le Mon, 30 Jul 2012 23:58:30 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :
> Le Fri, 27 Jul 2012 16:26:23 +0100,
> Will Newton <will.newton@gmail.com> a ?crit :
>
> > Signed-off-by: Will Newton <will.newton@imgtec.com>
>
> Applied, thanks. I did some changes to the package, though:
>
> - add dependencies on the supported architectures to avoid build
> failures on ARM and other unsupported arches
> - add a patch that removes an useless warning about the kernel
> version. This patch is present upstream. However since it
> modifies configure.ac, we need to autoreconf the package.
> - change AUTOTARGETS to autotools-package
Unfortunately, the sysprof package has a number of build problems on
x86 and ppc. See:
http://autobuild.buildroot.org/results/60728435af0221548c817cc8771674cc088e4d10/build-end.log
http://autobuild.buildroot.org/results/2d0ce96b30d32992d8f55f3a5974a81bbdb88915/build-end.log
It has been causing quite a few build failures since I merged the
package, so it would be good to fix those.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-31 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 15:26 [Buildroot] [PATCH] sysprof: New package Will Newton
2012-07-30 21:58 ` Thomas Petazzoni
2012-07-31 9:04 ` Thomas Petazzoni [this message]
2012-07-31 10:31 ` Will Newton
2012-07-31 10:35 ` Thomas Petazzoni
2012-08-01 8:03 ` Thomas Petazzoni
2012-08-02 7:19 ` 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=20120731110420.76490dd1@skate \
--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