From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: do we need patch-native ?
Date: Wed, 13 Oct 2010 08:26:43 -0600 [thread overview]
Message-ID: <4CB5C1A3.6000506@mlbassoc.com> (raw)
In-Reply-To: <AANLkTimmoNWm5fDxSBvR7MSUDBH8w0FyiRMFoR5WXuuf@mail.gmail.com>
On 10/13/2010 08:12 AM, Frans Meulenbroeks wrote:
> Hi,
>
> I had to do a build on OpenSuse 11.3 today, and it failed building
> quilt-native (0.46-r2)
>
> Root cause is that quilt configure tries to find whether patch is
> installed and has a version> 2.4
> It does so by calling patch --version and extract the version string from it.
>
> The patch from 11.3 identifies itself as:
> GNU patch 2.6.1.81-5b68
> However the quilt configure script expected to find output like:
> patch 2.6 (which is what I get on my ubuntu 10.4 version).
>
> I see several possible options to fix this:
> - make a package patch-native, so we can use our own patch
> - patch quilt so its configure can deal with both patch version strings
>
> Problem with the latter is that I have no idea how many other recipes
> will have a similar test (and definitely they are not all triggered by
> the images I regularly build.
> Therefore I think I have a preference to introduce patch-native, but I
> would like to hear how you guys& gals think about this, and whether
> you see other options.
Sounds like quilt's configure script is broken. Such behaviour
should not be catered to - it should be fixed.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-10-13 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 14:12 do we need patch-native ? Frans Meulenbroeks
2010-10-13 14:26 ` Gary Thomas [this message]
2010-10-13 17:58 ` Frans Meulenbroeks
-- strict thread matches above, loose matches on Subject: below --
2010-10-15 15:22 Alexander Stohr
2010-10-25 13:17 Alexander Stohr
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=4CB5C1A3.6000506@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@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 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.