On Sat, Jul 28, 2018 at 10:33 AM, Alexander Kanavin
wrote:
> Andre, do take a look at 1.1 as well. As soon as the final openssl
> 1.1.1 is released (and I get the powerful build box my new employer
> promised), I'll send a patchset that makes 1.1 the default - I'm not
> sure you should put all
Squash whitespace in CC_INFO to avoid recipe whitespace changes to
CFLAG affecting the final openssl binaries (the value of CC_INFO gets
embedded in libcrypto, via buildinf.h).
Signed-off-by: Andre McCurdy
---
meta/recipes-connectivity/openssl/openssl_1.0.2o.bb | 2 +-
1 file changed, 1
Previously (when EXTRA_OEMAKE contained -e) exporting these variables
over-rode default values in the top-level openssl Makefile. However,
since -e was removed from EXTRA_OEMAKE as part of:
http://git.openembedded.org/openembedded-core/commit/?id=537a404cfbb811fcb526cdb5f2e059257de6ef13
This patch adds a second line to the -help output of the CA.pl script
(which lists almost the same command line options as the line above
it but in a slightly different order). Although it's tagged as a
Debian backport, there's no patch like it in recent Debian patch sets
for openssl 1.0.2.
Creating the openssl manpages, which happens as part of do_install(),
can take a significant amount of time (e.g. ~50 seconds on a quad
core laptop). Provide a PACKAGECONFIG option to allow creation of the
manpages to be skipped completely if not required and inherit the
manpages class to
The fact that the darwin support only appears to consider x86 (and
not x86_64) suggests that it's not maintained or tested. In general
oe-core doesn't support building on darwin.
Signed-off-by: Andre McCurdy
---
meta/recipes-connectivity/openssl/openssl_1.0.2o.bb | 7 ---
1 file changed, 7
On Sat, Jul 28, 2018 at 4:57 AM, Burton, Ross wrote:
> You might want to use the manpages class here.
Thanks. I was wondering if I could justify disabling the manpages by
default for the target builds too and the api-documentation distro
feature does exactly that :-)
> On 28 July 2018 at 00:28,
Andre, do take a look at 1.1 as well. As soon as the final openssl
1.1.1 is released (and I get the powerful build box my new employer
promised), I'll send a patchset that makes 1.1 the default - I'm not
sure you should put all this effort into a soon obsolete version.
Alex
2018-07-28 1:27
On 27 July 2018 at 00:51, Christopher Clark
wrote:
> +ENABLE_EXTRA_TARGETS ?= "--enable-targets=${ARCH_EFI_EMULATION}"
This has an interesting implication in that it's not building support
for all targets now, specifically buildhistory-diff shows that large
chunks are no longer being built:
You might want to use the manpages class here.
Ross
On 28 July 2018 at 00:28, Andre McCurdy wrote:
> Creating the openssl manpages, which happens as part of do_install(),
> can take a significant amount of time (e.g. ~50 seconds on a quad
> core laptop). Provide a PACKAGECONFIG option to allow
rm_work if enabled leads to some tests failing that rely on artifacts
being present. Check if rm_work.bbclass is included and show an error
and exit if it is.
Fixes [YOCTO #12694]
Signed-off-by: Anuj Mittal
---
meta/lib/oeqa/selftest/context.py | 4
1 file changed, 4 insertions(+)
diff
From: Bruce Ashfield
Newer kernels (4.14/v4.15+) have dependencies for the build of
modules (and hence external modules). Without these dependencies
explicitly in the build chain, you can end up with build failures like:
work-shared/qemux86/kernel-source/scripts/extract-cert.c:21:25: fatal
From: Richard Purdie
Kernels which use tools/objtool can now fail when building external modules
due to objtool being missing, the generated files can also cause problems
for kernel-devsrc.
Ensure objtool is generated in make-mod-scripts by also calling
"make prepare".
For devsrc, delete the
13 matches
Mail list logo
