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: Thu, 14 Apr 2011 10:00:59 +0800 [thread overview]
Message-ID: <20110414020059.GA21398@qhe2-db> (raw)
In-Reply-To: <BANLkTikg2Bb8bCrnjJU3JyP0mHTYHFoRgg@mail.gmail.com>
On Wed, 2011-04-13 at 23:36 +0800, Khem Raj wrote:
> On Wed, Apr 13, 2011 at 2:26 AM, Qing He <qing.he@intel.com> wrote:
> > From: Qing He <qing.he@intel.com>
> >
> > fixes [YOCTO #969]
> >
> > Signed-off-by: Qing He <qing.he@intel.com>
> > ---
> > ??.../quilt/quilt/gnu_patch_test_fix_target.patch ?? ??| ?? 66 ++++++++++++++++++++
> > ??meta/recipes-devtools/quilt/quilt_0.48.bb ?? ?? ?? ?? ??| ?? ??6 +-
> > ??2 files changed, 70 insertions(+), 2 deletions(-)
> > ??create mode 100644 meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch
> >
> > diff --git a/meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch b/meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch
> > new file mode 100644
> > index 0000000..784fe76
> > --- /dev/null
> > +++ b/meta/recipes-devtools/quilt/quilt/gnu_patch_test_fix_target.patch
> > @@ -0,0 +1,66 @@
> > +The test of patch and diff should not be run for cross build,
> > +rather, assume them as gnu version is rather safe. This is a
> > +workaround to remove it altogether.
> > +
>
> why is this patch needed. I assume all linux distributions use GNU
> diff and patch
> and that what is being checked so why remove the checks ? these messages
> are atleast useful for folks who are trying other build hosts e.g. darwin
Because patch is used at runtime rather than build time. It is used
mainly in patch-wrapper and some other scripts.
configure.ac of quilt practically doesn't differentiate them,
this leads to problems in cross-compiling:
1. the QUILT_COMPAT_PROG_PATH finds the wrong patch, say we are
building on darwin with a non-GNU patch, host patch found in
/usr/bin or /sw/bin is irrelevant, what should be tested is
<target sysroot>/path/to/patch(which may not be /usr/bin), and
then @PATCH@ should be set to a value with <target sysroot>
removed.
2. the test is performed by running "patch --version", this obviously
doesn't work for cross-compiling.
The right way to do this may be something like:
if test "x$cross_compiling" = "xyes"; then
AC_CHECK_PROG in target sysroot
PATCH=strip sysroot in the absolute path
else
QUILT_COPAT_PROG_PATH
original test
fi
This is troublesome and error prone, since a separate SYSROOT needs to
be handled by configure, and target patch may as well not in a standard
path. The simplest way to do it is to remove the test, as we have
separate recipes for quilt and quilt-native.
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.
Thanks,
Qing
next prev parent reply other threads:[~2011-04-14 2:10 UTC|newest]
Thread overview: 12+ 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 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 [this message]
2011-04-14 15:23 ` Khem Raj
2011-04-15 9:19 ` Qing He
2011-04-15 14:22 ` Khem Raj
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
-- strict thread matches above, loose matches on Subject: below --
2011-04-25 9:49 [PATCH 0/2][RESEND] bug fix for quilt and sat-solver Qing He
2011-04-25 9:49 ` [PATCH 2/2] quilt: fix test for target build Qing He
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=20110414020059.GA21398@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 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.