From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: python-m2crypto-native broken
Date: Tue, 2 Oct 2012 21:49:06 -0400 [thread overview]
Message-ID: <20121003014906.GD32243@edge> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C2F589A@DFLE09.ent.ti.com>
On Tue, Oct 02, 2012 at 09:11:06PM -0400, Cooper Jr., Franklin wrote:
> I tried doing a cleanall on python-m2crypto-native and python-m2crypto since
> I figured that might be the potential issue. That did not solve the issue.
> The weird part is that it isn't a actually compile error it is a patch
> error. Is there something else I can try instead of deleting my entire temp
> directory?
Well, I don't think it has anything to do with the recent change, but rather
looks like the recipe is bad - when building from scratch, it first fails on
the bad checksums, and then when checksums are corrected, fails to apply the
first patch. Doing so manually fails the same way. So, I'm wondering how it
used to work for you before, but that's why it still works when re-using the
old temp/work directory...
--
Denys
prev parent reply other threads:[~2012-10-03 1:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 0:32 python-m2crypto-native broken Cooper Jr., Franklin
2012-10-03 0:59 ` Denys Dmytriyenko
2012-10-03 1:11 ` Cooper Jr., Franklin
2012-10-03 1:49 ` Denys Dmytriyenko [this message]
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=20121003014906.GD32243@edge \
--to=denys@ti.com \
--cc=fcooper@ti.com \
--cc=meta-arago@arago-project.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.