From: "Alexander Stohr" <Alexander.Stohr@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: patchutils 0.2.31 - not that compatible with state of the art automake
Date: Tue, 05 Oct 2010 20:20:41 +0200 [thread overview]
Message-ID: <20101005182041.23910@gmx.net> (raw)
oe uses version 0.2.31 of patchutils. i consider this a developers packages.
thats what is at the download location right now:
[ ] patchutils-0.2.31.tar.bz2 13-Jun-2005 17:46 143K
[ ] patchutils-0.3.0.tar.bz2 02-Jul-2008 12:07 146K
[ ] patchutils-0.3.1.tar.bz2 23-Jan-2009 18:06 155K
i was having noticeable trouble with those 5 years old version
since i am fiddling around with a relatively recent automake.
all the build behavior of patchutils was quite erratic.
staring and dealing the source package internals i reasoned
that those old version is probably not that automake compliant.
so i once took the probably most simple choice to solve it:
cp patchutils_0.2.31.bb patchutils_0.3.1.bb
that seemingly made me succeed with that recipes family.
regards, Alex.
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
next reply other threads:[~2010-10-05 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 18:20 Alexander Stohr [this message]
2010-10-06 16:02 ` patchutils 0.2.31 - not that compatible with state of the art automake 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=20101005182041.23910@gmx.net \
--to=alexander.stohr@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox