On 1 February 2016 at 18:50, Khem Raj wrote:
> I wonder if we should have a QA check to decipher that if .so is a not
> a symlink then provide this
> as an error right away until the recipe takes care of it with
> FILES_SOLIBS or something like that
>
That's exactly what I'm testing now :)
Ross
On Mon, Feb 1, 2016 at 5:33 AM, Burton, Ross wrote:
>
> On 29 January 2016 at 21:21, Burton, Ross wrote:
>>
>> And for even more fun the resulting package doesn't actually depend on
>> libssl, due to the layout confusing the shlibs code in package.bbclass.
>
>
> Sigh. Clearly I need a break. In
On 29 January 2016 at 21:21, Burton, Ross wrote:
> And for even more fun the resulting package doesn't actually depend on
> libssl, due to the layout confusing the shlibs code in package.bbclass.
>
Sigh. Clearly I need a break. Inserted a load of debugging and then the
obvious jumped out at me
On 29 January 2016 at 17:13, Burton, Ross wrote:
> This should at least hard-code --with-nss or --with-openssl (and the
> relevant build dependency), at the moment you're relying on the sysroot
> containing NSS or openssl. Luckily something pulls in openssl but that may
> change.
>
And for even
On 29 January 2016 at 15:07, Ioan-Adrian Ratiu wrote:
> +PACKAGECONFIG[crypto] = "--with-crypto,--without-crypto"
>
configure: Crypto was requested but no crypto library was found;
autodetecting possible libraries
checking openssl/x509.h usability... yes
checking openssl/x509.h presence... yes
c
Enable apr-util's cryptographic routines so that the apache2 package
can encrypt session data. Also add sqlite3 and ldap modules, disabled
by default.
Signed-off-by: Adam Chappell
Signed-off-by: Jacob Champion
Signed-off-by: Ioan-Adrian Ratiu
Acked-by: Ken Sharp
---
meta/recipes-support/apr/a
