From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2010-10-14 - configure epiphany still fails
Date: Wed, 20 Oct 2010 13:08:05 +0200 [thread overview]
Message-ID: <4CBECD95.1050700@dresearch.de> (raw)
In-Reply-To: <DB561678F08F554EB0D9F21B70E268A505AF50@exchange.intern.dresearch.de>
On 10/17/2010 02:27 PM, Sledz, Steffen wrote:
> do_configure still fails with the ca-certificates problem [1]. :(
>
> If nobody will find a solution for this problem (for my first diagnosis see [2]) until the next testing branch creation, i'll push my original patch which disables the ca-file use [3].
>
> Steffen
>
> [1] <http://tinderbox.openembedded.org/packages/859111/>
> [2] <http://thread.gmane.org/gmane.comp.handhelds.openembedded/37925/focus=38034>
> [3] <http://thread.gmane.org/gmane.comp.handhelds.openembedded/37453/focus=37585>
OK, i tried to fix for myself. Patches follow.
Steffen
next prev parent reply other threads:[~2010-10-21 6:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 21:56 testing branch 2010-10-14 Cliff Brake
2010-10-15 10:21 ` Cliff Brake
2010-10-16 7:24 ` Petr Štetiar
2010-10-19 6:21 ` Frans Meulenbroeks
2010-10-19 11:06 ` Cliff Brake
2010-10-19 11:13 ` Koen Kooi
2010-10-17 12:27 ` testing branch 2010-10-14 - configure epiphany still fails Sledz, Steffen
2010-10-20 11:08 ` Steffen Sledz [this message]
2010-10-20 11:10 ` [PATCH 1/2] ca-certificates: unbreak do_configure of packages depending on ca-bundle.pem Steffen Sledz
2010-10-21 9:59 ` Thomas Zimmermann
2010-10-20 11:10 ` [PATCH 2/2] epiphany-2.30.2: unbreak do_configure by setting ca-file path Steffen Sledz
2010-10-21 9:14 ` Steffen Sledz
2010-10-21 9:54 ` Holger Freyther
2010-10-21 12:11 ` Steffen Sledz
2010-10-23 12:27 ` Sledz, Steffen
2010-10-25 9:55 ` [PATCH v2] " Steffen Sledz
2010-10-25 10:03 ` Steffen Sledz
2010-10-25 11:37 ` Paul Menzel
2010-10-25 12:07 ` Steffen Sledz
2010-10-25 15:36 ` Steffen Sledz
2010-10-25 18:02 ` 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=4CBECD95.1050700@dresearch.de \
--to=sledz@dresearch.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