Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2010-10-08
Date: Mon, 11 Oct 2010 18:06:21 +0200	[thread overview]
Message-ID: <i8vclt$9te$1@dough.gmane.org> (raw)
In-Reply-To: <DB561678F08F554EB0D9F21B70E268A505AF2A@exchange.intern.dresearch.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11-10-10 17:34, Sledz, Steffen wrote:
> On 10/11/2010 09:34 AM, Sledz, Steffen wrote:
>> do_configure still fails for epiphany-2.30.2-r3 (see
>> <http://tinderbox.openembedded.net/packages/835265/>) with:
>>
>> "checking location of system Certificate Authority list...
>> configure: error: could not find. Use --with-ca-file=path
>> to set, or --without-ca-file to disable"
>>
>> I thought the additional ca-certifactes dependency (see thread
>> <http://thread.gmane.org/gmane.comp.handhelds.openembedded/37453/focus=37585>)
>> fixes this, but it does not seem so. :(
>>
>> I'd a look into my openSUSE-system and there epiphany uses
>> a file /var/lib/ca-certificates/ca-bundle.pem (linked to
>> /etc/ssl/ca-bundle.pem) installed by the ca-certificates package.
>>
>> The OE ca-certificates package does not install such a bundle.
>> So may be that's the real problem.
> 
> A look into the ca-certificates recipe shows this:
> 
>   pkg_postinst_${PN} () {
>           /usr/sbin/update-ca-certificates
>   }
> 
> I think this is to late if another package needs the result from this call in its configuration stage.

That's missing a $D check as well, since in that form it can't be run
off-line

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMszX9MkyGM64RGpERAntxAJ4ks0QTGm4TYe0I4oFZkJkVibnYxQCfX383
lMq5v0la+u26N9XyIUdTVFk=
=6Bnt
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-10-11 16:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 21:35 testing branch 2010-10-08 Cliff Brake
2010-10-09  7:10 ` Frans Meulenbroeks
2010-10-09 20:58   ` Frans Meulenbroeks
2010-10-09 22:55     ` Michael 'Mickey' Lauer
2010-10-10  8:20       ` Paul Menzel
2010-10-10  9:13         ` Khem Raj
2010-10-10  9:38           ` Paul Menzel
2010-10-10 19:29             ` Khem Raj
2010-10-10 19:37               ` Paul Menzel
2010-10-10 20:27                 ` Khem Raj
2010-10-10 19:50               ` commit messages (was: testing branch 2010-10-08) Paul Menzel
2010-10-12 12:30                 ` Cliff Brake
2010-10-09 23:30   ` testing branch 2010-10-08 Graham Gower
2010-10-12 21:12     ` Cliff Brake
2010-10-12 21:15       ` Frans Meulenbroeks
2010-10-11  7:34 ` Sledz, Steffen
2010-10-11 15:34   ` Sledz, Steffen
2010-10-11 16:06     ` Koen Kooi [this message]
2010-10-12 18:06       ` Sledz, Steffen
2010-10-13 16:36 ` Petr Štetiar
2010-10-13 18:10   ` 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='i8vclt$9te$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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