From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] epiphany-2.30.2: unbreak do_configure by setting ca-file path
Date: Mon, 25 Oct 2010 12:03:19 +0200 [thread overview]
Message-ID: <4CC555E7.2010000@dresearch.de> (raw)
In-Reply-To: <1288000524-18800-1-git-send-email-sledz@dresearch.de>
Am 25.10.2010 11:55, schrieb Steffen Sledz:
> * Disable existence check for ca-bundle file in configure.ac because
> it does not work in OE cross compile environment (location at build
> host may differ from location at target).
> * Explicitely set ca-bundle file path according to the one used by
> ca-certificates package.
>
> Signed-off-by: Steffen Sledz <sledz@dresearch.de>
This is a patch implementing the first option i mentioned (Use the --with-ca-file option but disable the existance check in configure.ac).
If there are no better solutions in the next time i'll push this one.
Steffen
next prev parent reply other threads:[~2010-10-25 10:03 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
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 [this message]
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=4CC555E7.2010000@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 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.