mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Wang Nan <wangnan0@huawei.com>,
	linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Geng Hui <hui.geng@huawei.com>
Subject: Re: [PATCH] tools lib traceevent: Use realpath for srctree and objtree
Date: Wed, 25 Feb 2015 01:30:52 +0100	[thread overview]
Message-ID: <20150225003052.GB8478@krava.redhat.com> (raw)
In-Reply-To: <20150223210932.10d2338b@grimm.local.home>

On Mon, Feb 23, 2015 at 09:09:32PM -0500, Steven Rostedt wrote:
> Another email inbox clean up: BLAST FROM THE PAST
> 
> On Fri, 7 Feb 2014 12:22:33 +0800
> Wang Nan <wangnan0@huawei.com> wrote:
> 
> > If BUILD_SRC or CURDIR contains tailing '/', the file names passed to gcc will
> > contain '//'. It will be contained .o's in debuginfo, then confuse debugedit:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=304121
> > 
> > This patch uses realpath command to makesure potential tailing '/'s are removed.
> 
> Is this still an issue? I know Jiri did a bunch of changes to the make
> process, but does this still confuse debugedit (whatever that is)?

this should no longer be an issue.. recent build changes
take care of this

jirka

      reply	other threads:[~2015-02-25  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07  4:22 Wang Nan
2015-02-24  2:09 ` Steven Rostedt
2015-02-25  0:30   ` Jiri Olsa [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=20150225003052.GB8478@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hui.geng@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=wangnan0@huawei.com \
    /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

all inboxes | Powered by JetHome®