All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>, Michal Marek <mmarek@suse.cz>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
	David Howells <dhowells@redhat.com>, Borislav Petkov <bp@suse.de>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] tools: unbreak 'make tools/*'
Date: Thu, 19 Mar 2015 09:11:03 -0700	[thread overview]
Message-ID: <20150319161103.GC19571@brian-ubuntu> (raw)
In-Reply-To: <20150319142026.GE6363@krava>

On Thu, Mar 19, 2015 at 03:20:26PM +0100, Jiri Olsa wrote:
> On Thu, Mar 19, 2015 at 10:39:25AM -0300, Arnaldo Carvalho de Melo wrote:
> 
> SNIP
> 
> > [acme@ssdandy linux]$
> > 
> > -------------------------------------------------------
> > 
> > Jiri, can you take a look at the above?
> > 
> > It works if I use 'make -C', with O=, like I usually do, or without it:
> > 
> > -------------------------------------------------------
> > 
> > [acme@ssdandy linux]$ make -C tools/perf
> > make: Entering directory `/home/acme/git/linux/tools/perf'
> >   BUILD:   Doing 'make -j8' parallel build
> > 
> > Auto-detecting system features:
> > ...                         dwarf: [ on  ]
> > ...                         glibc: [ on  ]
> > <SNIP>
> > ...                     libunwind: [ OFF ]
> > ...            libdw-dwarf-unwind: [ on  ]
> > ...                          zlib: [ on  ]
> > 
> > config/Makefile:308: No libunwind found. Please install libunwind-dev[el] >= 1.1 and/or set LIBUNWIND_DIR
> > config/Makefile:598: No libbabeltrace found, disables 'perf data' CTF format support, please install libbabeltrace-dev[el]/libbabeltrace-ctf-dev
> >   GEN      common-cmds.h
> >   CC       util/abspath.o
> >   CC       ui/setup.o
> >   CC       arch/common.o
> > 
> > 
> > -------------------------------------------------------
> > 
> > Can you please check these issues, using my perf/core branch at:
> 
> hum, I've never cared about tools/Makefile :-\
> 
> so this is what we want to be able to do/use? :
> 
>   $ make tools/
>   $ make tools/perf
>   $ make O=$(BUILDDIR) tools/perf

Honestly, I only was caring about 'make tools/tmon' but noticed other
things were broken. I'd be OK if we didn't support building from the
top-level directory (it's just confusing things here), but since we
advertise the feature, it'd really better work!

> it ^^^ does not work for me even with this patch
> (tools/Makefile still using 'libapikfs' being first issue I saw)
> 
> I'll check and send fix

Yeah, I'm not likely to spend time on an updated fix real soon. Consider
my patch a bug report, if the suggested fix doesn't work out. I'm not
much of a build system expert here.

Thanks,
Brian

      reply	other threads:[~2015-03-19 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29  4:47 [PATCH] tools: unbreak 'make tools/*' Brian Norris
2015-01-29  4:47 ` Brian Norris
2015-02-02 23:43 ` Brian Norris
2015-02-03  0:07   ` Arnaldo Carvalho de Melo
2015-03-19 13:39 ` Arnaldo Carvalho de Melo
2015-03-19 14:20   ` Jiri Olsa
2015-03-19 16:11     ` Brian Norris [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=20150319161103.GC19571@brian-ubuntu \
    --to=computersforpeace@gmail.com \
    --cc=acme@kernel.org \
    --cc=bp@suse.de \
    --cc=dhowells@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.