linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "acme@redhat.com" <acme@redhat.com>
Cc: "mingo@kernel.org" <mingo@kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bp@suse.de" <bp@suse.de>, "jolsa@kernel.org" <jolsa@kernel.org>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 0/5] Perf fixes for ARC + uClibc
Date: Fri, 9 Jan 2015 18:47:08 +0000	[thread overview]
Message-ID: <1420829227.5917.5.camel@synopsys.com> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA2307565BCA4D7@IN01WEMBXA.internal.synopsys.com>

Hi Arnaldo,

On Wed, 2015-01-07 at 07:38 +0000, Vineet Gupta wrote:
> On Tuesday 06 January 2015 08:43 PM, Arnaldo Carvalho de Melo wrote:
> 
> > Em Tue, Jan 06, 2015 at 07:22:10PM +0530, Vineet Gupta escreveu:
> > > > Hi,
> > > > 
> > > > This series based off linux-next of 20150105 allows us to build/use perf
> > > > for ARC with uClibc based userland.
> > Do you have some ready made ARC VM image with devel tools I could use with qemu?
> > 
> > - Arnaldo
> >  
> 
> FWIW, most of the issues I posted fixes for can be reproduced with
> building perf with ARC buildroot !
> 
> git://github.com:foss-for-synopsys-dwc-arc-processors/buildroot.git

To reproduce described build problems (covered in patches 1, 2, 3, 5) you may indeed use Buildroot.
Just get the most recent release from here http://buildroot.uclibc.org/downloads/buildroot-2014.11.tar.gz
and use load following configuration in "menuconfig":
--->---
BR2_arcle=y
BR2_TOOLCHAIN_BUILDROOT_LARGEFILE=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_DEFCONFIG="fpga"
BR2_PACKAGE_PERF=y
BR2_TARGET_ROOTFS_INITRAMFS=y 
--->---

Then say "make" and you'll see the problem.
If you experience any problems trying to follow my advice please let me
know and I'll try to help you.

-Alexey

      reply	other threads:[~2015-01-09 18:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 13:52 [PATCH 0/5] Perf fixes for ARC + uClibc Vineet Gupta
2015-01-06 13:52 ` [PATCH 1/5] perf tools: [uclibc] fix statfs.f_type data type mismatch build error Vineet Gupta
2015-01-06 13:52 ` [PATCH 2/5] perf tools: [uclibc] Elide strlcpy warning Vineet Gupta
2015-01-06 13:52 ` [PATCH 3/5] perf tools: [uclibc] Avoid build splat for syscall numbers Vineet Gupta
2015-01-06 13:52 ` [PATCH 4/5] perf tools: [uclibc] don't rely on glibc malloc working for sz 0 Vineet Gupta
2015-01-08  7:51   ` Namhyung Kim
2015-01-10 10:16     ` Vineet Gupta
2015-01-10 10:44       ` Namhyung Kim
2015-01-06 13:52 ` [PATCH 5/5] perf tools: [uclibc] provide stub for pthread_attr_setaffinity_np Vineet Gupta
2015-01-08  7:56   ` Namhyung Kim
2015-01-10 10:30     ` Vineet Gupta
2015-01-06 15:13 ` [PATCH 0/5] Perf fixes for ARC + uClibc Arnaldo Carvalho de Melo
2015-01-07  5:16   ` Vineet Gupta
2015-01-07  7:38   ` Vineet Gupta
2015-01-09 18:47     ` Alexey Brodkin [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=1420829227.5917.5.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=acme@redhat.com \
    --cc=bp@suse.de \
    --cc=jolsa@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).