Am 21.10.2010 14:11, schrieb Steffen Sledz:
> Am 21.10.2010 11:54, schrieb Holger Freyther:
>> It doesn't look correct. Judging from the code epiphany
>> will now look into ${STAGING_DIR_HOST}/etc/ssl/ca-bundle.pem
>> at runtime.
>
> OK, you're right.
>
>> What about stripping away this and use the etcdir variable?
>
> Sorry, no idea how to do this. Do you have an example?
I've done some further investigations here.
The problem is that the configure script checks for the ca-file (tries some
default locations, or uses the given path) *at build time at the build host*
und uses the resulting path *at runtime at the target*.
I believe this is an error in the epiphany package itself.
I see two options here (i prefer the 1st):
1. Use the --with-ca-file option but disable the existance check in configure.ac
2. Use --without-ca-file.
Both would obsolete the related patch i suggested for ca-certificates recipe.
Any other options?
BTW: Why does this error comes up in my builds and not in others?
I think the cause are the default locations configure tries. These are
/etc/pki/tls/certs/ca-bundle.crt and /etc/ssl/certs/ca-certificates.crt.
I use openSUSE-11.3 as build host which puts its own ca bundle at
/etc/ssl/ca-bundle.pem. May be Fedore or Ubuntu use one of the locations
mentioned above.
Steffen
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
