Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Qing He <qing.he@intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] quilt: fix test for target build
Date: Fri, 15 Apr 2011 17:19:05 +0800	[thread overview]
Message-ID: <20110415091905.GC21398@qhe2-db> (raw)
In-Reply-To: <BANLkTi=Y454r0KQuorJM2HxUafA+Gkzmag@mail.gmail.com>

On Thu, 2011-04-14 at 23:23 +0800, Khem Raj wrote:
> > The reason to touch this part of code is that the test itself doesn't
> > work for newer versions of GNU patch, see:
> > ??http://lists.nongnu.org/archive/html/quilt-dev/2010-06/msg00002.html
> > This surely fixes the configure error, but is logically not suitable for
> > cross compiling.
> 
> As I understand you are trying to fix quilt target recipe. Then may it
> will be better to take the above
> patch for both target and native but apply this
> workaround conditionally only for target recipe

This was once backported, but subsequently reverted, see:
  http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=ec740ac770d2124cbae1ab936d85b8343076c53b

autoconf-native is not available at the point of quilt-native, so
autoreconf is not desirable. This is also the reason for separation
of quilt and quilt-native from the very beginning.

Apart from that, the workaround is solely for target recipe.

> 
> there are options --with-patch --with-diff also
> there to point these utilities

The problem still lies in cross building:
  --with-patch=${bindir}/patch          at build time, it's /usr/bin/patch
                                        which is host utility, if target
					${bindir} /= /usr/bin, the file
					may not exist.

  --with-patch=${STAGING_BINDIR}/patch  causes runtime error as
                                        ${STAGING_BINDIR} leaks into target scripts

  --with-patch=patch                    this may work, but may fail (in case
                                        the target scripts unset PATH)

This is the problem of such tests without the concept of a target
sysroot.

Thanks,
Qing



  reply	other threads:[~2011-04-15  9:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  9:26 [PATCH 0/2] bug fix for quilt and sat-solver Qing He
2011-04-13  9:26 ` [PATCH 1/2] sat-solver: fix arch=all packages Qing He
2011-04-13 15:38   ` Khem Raj
2011-04-14  3:20     ` Qing He
2011-04-13  9:26 ` [PATCH 2/2] quilt: fix test for target build Qing He
2011-04-13 15:36   ` Khem Raj
2011-04-13 16:48     ` Saul Wold
2011-04-14  2:00     ` Qing He
2011-04-14 15:23       ` Khem Raj
2011-04-15  9:19         ` Qing He [this message]
2011-04-15 14:22           ` Khem Raj

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=20110415091905.GC21398@qhe2-db \
    --to=qing.he@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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