Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] insane.bbclass: fix package_qa_check_buildpaths
Date: Wed, 16 Sep 2015 16:26:18 +0100	[thread overview]
Message-ID: <1442417178.26666.117.camel@linuxfoundation.org> (raw)
In-Reply-To: <55F97519.5000600@windriver.com>

On Wed, 2015-09-16 at 21:56 +0800, Robert Yang wrote:
> On 09/16/2015 08:38 PM, Richard Purdie wrote:
> > On Tue, 2015-09-15 at 19:28 -0700, Robert Yang wrote:
> >> * Ignore elf files because they usually contain build path:
> >>    - The path of the source file such as .c, these are usually happen
> >>      when separate B and S since we use absolute path to run configure
> >>      script, and then VPATH in Makefile will be an absolute path and
> >>      contains build path, we can use relative path in autotools.bbclass
> >>      to fix the problem, but we don't have to since they are harmless.
> >>    - The configure options such as "configure --with-libtool-sysroot"
> >>    - The compile options such as "gcc --sysroot"
> >>    These are harmless usually, so ignore elf files.
> >
> > I'm not sure about this. Yes, elf files have large issues in the debug
> > symbols but the main elf files really shouldn't have build paths in
> > them. I understand they can creep in through a variety of sources
> > including B!=S but we should really be identifying them and fixing them,
> > not pretending they don't exist. The whole point of this check
> > originally was to get to the bottom of this!
> 
> Thanks, the fix will change a lot to the build behaviour, I'd like to fix
> them in 2.1.

Agreed, this is 2.1 material at this point.

Cheers,

Richard



  reply	other threads:[~2015-09-16 15:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  2:28 [PATCH 0/4] meta: resend patches Robert Yang
2015-09-16  2:28 ` [PATCH 1/4] gtk+/cairo: enable x11 or directfb Robert Yang
2015-09-16 10:25   ` Jussi Kukkonen
2015-09-16 10:34     ` Robert Yang
2015-09-18 20:23       ` Burton, Ross
2015-09-22  2:40         ` Robert Yang
2015-09-22 14:12           ` Burton, Ross
2015-09-16  2:28 ` [PATCH 2/4] libsdl: depends on libglu when both x11 and opengl Robert Yang
2015-09-16  2:28 ` [PATCH 3/4] insane.bbclass: fix package_qa_check_buildpaths Robert Yang
2015-09-16 12:38   ` Richard Purdie
2015-09-16 13:56     ` Robert Yang
2015-09-16 15:26       ` Richard Purdie [this message]
2015-09-16  2:28 ` [PATCH 4/4] insane.bbclass: make package_qa_clean_path return a relative path Robert Yang

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=1442417178.26666.117.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.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