The old URL can't be available, give the new URL to keynote.
The project already moved to:
https://sourceforge.net/projects/keynote-2-3/
The different between old and new tarball was:
the old tarball contains doc directory, source codes were same.
Signed-off-by: Dengke Du
---
recipes-
When I build for x86_64 I found I needed to enable multilib to be able to
build u-boot (actually lib32_u-boot). U-boot now builds.
However 'bitbake edison-image -c populate_sdk' now errors with
Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING
Signed-off-by: Armin Kuster
---
...ate-tpm-key-support-well-known-key-option.patch | 99
.../files/0002-libtpm-support-env-TPM_SRK_PW.patch | 80 +++
.../files/0003-Fix-not-building-libtpm.la.patch| 25 ++
...-tpm-engine-parse-an-encrypted-tpm-SRK-pa.patch | 254 ++
Signed-off-by: Armin Kuster
---
.../tpm2-abrmd/files/tpm2-abrmd-init.sh| 65 ++
.../tpm2-abrmd/files/tpm2-abrmd.default| 1 +
.../recipes-tpm/tpm2-abrmd/tpm2-abrmd_1.1.1.bb | 54 ++
3 files changed, 120 insertions(+)
create mode 10
Signed-off-by: Armin Kuster
---
.../tpm-quote-tools/tpm-quote-tools_1.0.4.bb | 23 ++
1 file changed, 23 insertions(+)
create mode 100644
meta-tpm/recipes-tpm/tpm-quote-tools/tpm-quote-tools_1.0.4.bb
diff --git a/meta-tpm/recipes-tpm/tpm-quote-tools/tpm-quote-tools_1.
Signed-off-by: Armin Kuster
---
meta-tpm/recipes-tpm/pcr-extend/pcr-extend_git.bb | 25 +++
1 file changed, 25 insertions(+)
create mode 100644 meta-tpm/recipes-tpm/pcr-extend/pcr-extend_git.bb
diff --git a/meta-tpm/recipes-tpm/pcr-extend/pcr-extend_git.bb
b/meta-tpm/recipe
Op Fri, 25 Aug 2017 22:30:42 +, schreef Ferry Toth:
> Op Fri, 25 Aug 2017 21:22:40 +0200, schreef Ferry Toth:
>
>> Khem Raj wrote:
>>
>>
>>
>>>
>>> On 8/23/17 3:40 PM, Ferry Toth wrote:
Op Wed, 23 Aug 2017 14:51:55 -0700, schreef Khem Raj:
> On 8/23/17 2:29 PM, Ferry Toth w
Hi Ross,
DEPENDS += "bc-native dtc-native"
+DEPENDS_append = " python-native"
+DEPENDS_append_x86-64 = " iasl-native swig-native"
Don't _append when you can just extend the assignment above.
I just did it that way for the moment since I wanted to circumvent merge
conflicts when I upgrade the
2017-10-08 5:39 GMT+02:00 Trevor Woerner :
> On Sat, Oct 7, 2017 at 7:03 PM, Mirza Krak wrote:
Thank you for taking the time and explaining the current and previous
state. It is highly appreciated.
>> As I started digging to check the current state of the different
>> layers it was quite clear
