[yocto] [meta-security][PATCH] meta-tpm: add runtime test for tpm2

2019-03-21 Thread Armin Kuster 
This runs a basic tpm test using the simulator

Signed-off-by: Armin Kuster 
---
 meta-tpm/lib/oeqa/runtime/cases/tpm2.py | 41 +
 1 file changed, 41 insertions(+)
 create mode 100644 meta-tpm/lib/oeqa/runtime/cases/tpm2.py

diff --git a/meta-tpm/lib/oeqa/runtime/cases/tpm2.py 
b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py
new file mode 100644
index 000..d92b15c
--- /dev/null
+++ b/meta-tpm/lib/oeqa/runtime/cases/tpm2.py
@@ -0,0 +1,41 @@
+from oeqa.runtime.case import OERuntimeTestCase
+from oeqa.core.decorator.depends import OETestDepends
+from oeqa.runtime.decorator.package import OEHasPackage
+
+
+class Tpm2Test(OERuntimeTestCase):
+def check_endlines(self, results,  expected_endlines): 
+for line in results.splitlines():
+for el in expected_endlines:
+if line == el:
+expected_endlines.remove(el)
+break
+
+if expected_endlines:
+self.fail('Missing expected line endings:\n  %s' % '\n  
'.join(expected_endlines))
+
+@OEHasPackage(['tpm2.0-tss'])
+@OEHasPackage(['tpm2-abrmd'])
+@OEHasPackage(['tpm2.0-tools'])
+@OEHasPackage(['ibmswtpm2'])
+@OETestDepends(['ssh.SSHTest.test_ssh'])
+def test_tpm2_sim(self):
+cmds = [
+'tpm_server &',
+'tpm2-abrmd --allow-root --tcti=mssim &'
+   ]
+
+for cmd in cmds:
+status, output = self.target.run(cmd)
+self.assertEqual(status, 0, msg='\n'.join([cmd, output]))
+
+@OETestDepends(['tpm2.Tpm2Test.test_tpm2_sim'])
+def test_tpm2(self):
+ (status, output) = self.target.run('tpm2_pcrlist')
+ expected_endlines = []
+ expected_endlines.append('sha1 :')
+ expected_endlines.append('  0  : 
0003')
+ expected_endlines.append('  1  : 
')
+
+ self.check_endlines(output, expected_endlines)
+
-- 
2.17.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to add task only if flag set

2019-03-21 Thread Timothy Froehlich 
I'm working with a read only file system and I'm working on splitting
packages so that their config dirs are symlinked in from the persistent
data partition. But I'd like to be able to enable or disable this
optionally, so that I can still build an image with a r/w file system and a
single partition for easier development. I've got a class file with a new
task that moves config files to /data and symlinks them back, but I can't
figure out how to conditionally enable it. Ideally it'd be enabled only if
read-only-rootfs is set in IMAGE_FEATURES.

Here's the class if it helps:

ORIGINAL_FILES ??= "file1 file2..."
SYMLINK_NAMES ??= "sym1 sym2..."

do_symlink_to_data () {
install -d ${D}/${PERSIST_DIR}

ORIG_ARR=(${ORIGINAL_FILES})
SYMLINK_ARR=(${SYMLINK_NAMES})

for i in ${!ORIG_ARR[*]}; do
ORIG=ORIG_ARR[i]
SYMLINK=SYMLINK_ARR[i]


mv ${D}/$ORIG ${D}/${PERSIST_DIR}/$SYMLINK
ln -sr ${D}/${PERSIST_DIR}/$SYMLINK ${D}/$ORIG
done
}

FILES_${PN}_append_mender-image += " ${SYMLINK_NAMES}"

addtask symlink_to_data after do_install




-- 
Tim Froehlich
Embedded Linux Engineer
tfroehl...@archsys.io
215-218-8955
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] [kernel-cache][master][PATCH 0/3] support for Intel virtual RAID

2019-03-21 Thread Bruce Ashfield 
On Wed, Mar 20, 2019 at 11:44 PM Liwei Song  wrote:
>
> Hi Bruce,
>
> These three patches used to built-in nvme driver and efivarfs driver to kernel
> to make boot from Intel Virtual disk work.
> Also enable CONFIG_VMD kernel configuration
>
> Aim at master branch.
>

Thanks, this is now merged to master

Bruce

> Thanks,
> Liwei.
>
> Liwei Song (3):
>   intel-x86: built-in nvme driver to support boot from nvme disk
>   cfg/efi.cfg: built-in CONFIG_EFIVAR_FS to support Intel VROC
>   intel-x86: add Intel VMD support
>
>  bsp/intel-x86/intel-x86-64.scc   | 1 +
>  bsp/intel-x86/intel-x86.cfg  | 2 +-
>  cfg/efi.cfg  | 2 +-
>  features/intel-vmd/intel-vmd.cfg | 1 +
>  features/intel-vmd/intel-vmd.scc | 4 
>  5 files changed, 8 insertions(+), 2 deletions(-)
>  create mode 100644 features/intel-vmd/intel-vmd.cfg
>  create mode 100644 features/intel-vmd/intel-vmd.scc
>
> --
> 2.18.1
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH] x86/resctrl: Rename INTEL_RDT to RESCTRL

2019-03-21 Thread Bruce Ashfield 
On Wed, Mar 20, 2019 at 10:05 PM He Zhe  wrote:
>
>
>
> On 3/21/19 9:54 AM, He Zhe wrote:
> >
> > On 3/21/19 2:47 AM, Bruce Ashfield wrote:
> >> On Wed, Mar 20, 2019 at 3:24 AM  wrote:
> >>> From: He Zhe 
> >>>
> >>> The following upstream commits have renamed INTEL_RDT to RESCTRL.
> >>> 6fe07ce35e8a ("x86/resctrl: Rename the config option INTEL_RDT to 
> >>> RESCTRL")
> >>> e6d429313ea5 ("x86/resctrl: Avoid confusion over the new X86_RESCTRL 
> >>> config")
> >>>
> >> You forgot to mention which kernel versions this was for. Looking at
> >> the commits you
> >> are referencing, only 5.0 has them, so I assume you are looking at 5.0
> >> and master ?
> > Yes, only for 5.0
>
> and master, of course.
>

This is now staged on both branches.

Bruce

> Zhe
>
> >
> > Zhe
> >
> >> Bruce
> >>
> >>> Signed-off-by: He Zhe 
> >>> ---
> >>>  bsp/intel-x86/intel-x86-64.cfg | 4 ++--
> >>>  bsp/intel-x86/intel-x86.cfg| 4 ++--
> >>>  2 files changed, 4 insertions(+), 4 deletions(-)
> >>>
> >>> diff --git a/bsp/intel-x86/intel-x86-64.cfg 
> >>> b/bsp/intel-x86/intel-x86-64.cfg
> >>> index e66b93b..cd09102 100644
> >>> --- a/bsp/intel-x86/intel-x86-64.cfg
> >>> +++ b/bsp/intel-x86/intel-x86-64.cfg
> >>> @@ -40,8 +40,8 @@ CONFIG_CRYPTO_DEV_QAT_C62XVF=m
> >>>  CONFIG_CRYPTO_DEV_QAT_DH895xCC=m
> >>>  CONFIG_CRYPTO_DEV_QAT_DH895xCCVF=m
> >>>
> >>> -# Intel Resource Director Technology support
> >>> -CONFIG_INTEL_RDT=y
> >>> +# x86 CPU resource control support
> >>> +CONFIG_X86_CPU_RESCTRL=y
> >>>
> >>>  # Processor type and features
> >>>  CONFIG_NR_CPUS=256
> >>> diff --git a/bsp/intel-x86/intel-x86.cfg b/bsp/intel-x86/intel-x86.cfg
> >>> index dff54fe..548a620 100644
> >>> --- a/bsp/intel-x86/intel-x86.cfg
> >>> +++ b/bsp/intel-x86/intel-x86.cfg
> >>> @@ -342,8 +342,8 @@ CONFIG_TOUCHSCREEN_ZFORCE=m
> >>>  CONFIG_DRM_NOUVEAU=m
> >>>  CONFIG_DRM_NOUVEAU_BACKLIGHT=y
> >>>
> >>> -# Intel RDT support
> >>> -CONFIG_INTEL_RDT=y
> >>> +# x86 CPU resource control support
> >>> +CONFIG_X86_CPU_RESCTRL=y
> >>>
> >>>  # Intel RAPL
> >>>  CONFIG_IOSF_MBI=y
> >>> --
> >>> 2.7.4
> >>>
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] v4.18.x - stable updates comprising v4.18.32

2019-03-21 Thread Bruce Ashfield 
On Thu, Mar 21, 2019 at 3:17 PM Paul Gortmaker
 wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.30 release.
>
> There are about 165 commits here, based on commits chosen from what
> were used in the existing 4.19.29 --> 4.19.30 stable releases.
> Nothing unusual to report in this release, just the routine sort of
> stable type commits once again.  Which is a good thing!
>
> I've put this 4.18.x queue through the usual testing; build testing
> on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis
> and finally some sanity runtime tests on x86-64.
>
> I did the signed tag just as per the previously released versions.
> Please find a signed v4.18.32 tag using this key:
>
> http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6
>
> in the repo in the kernel.org directory here:
>
>https://git.kernel.org/cgit/linux/kernel/git/paulg/linux-4.18.y.git/
>git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git
>

Thanks. This has now been queued.

Bruce

> for merge to standard/base in linux-yocto-4.18 and then out from there
> into the other base and BSP branches.
>
> For those who are interested, the evolution of the commits is here:
>
>https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/
>
> This repo isn't needed for anything; it just exists for transparency and
> so people can see the evolution of the raw commits that were originally
> selected to create this 4.18.x release.
>
> Paul.



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH 4.18-rt] of: phandle_cache merge fixup for preempt-rt

2019-03-21 Thread Bruce Ashfield 
Thanks Paul, this is now merged.

Bruce

On Thu, Mar 21, 2019 at 3:12 PM Paul Gortmaker
 wrote:
>
> In yocto merge 5cc3fddf0e2a ("Merge branch 'v4.18/standard/base' into
> v4.18/standard/preempt-rt/base") there was a conflict between the
> backport of upstream b8a9ac1a5b99 ("of: of_node_get()/of_node_put() nodes
> held in phandle cache") and the rt-specific commit b75caf08b721 ("of:
> allocate / free phandle cache outside of the devtree_lock")
>
> Unfortunately the conflict resolution left a shadow variable introduced
> by the rt patch as undefined, resulting in:
>
> drivers/of/base.c:120:2: error: 'shadow' undeclared (first use in this 
> function)
>   shadow = phandle_cache;
>   ^~
>
> drivers/of/base.c: In function 'of_populate_phandle_cache':
> drivers/of/base.c:182:7: warning: 'shadow' is used uninitialized in this 
> function [-Wuninitialized]
>
> Here we create a merge fix-up that basically aligns the impacted code to
> match what is currently found in the 4.19-rt (as of v4.19.15-rt12).
>
> Reported-by: Yue Tao 
> Signed-off-by: Paul Gortmaker 
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 904c7686f9d7..4a33ef482bcc 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -106,31 +106,34 @@ static u32 phandle_cache_mask;
>  /*
>   * Caller must hold devtree_lock.
>   */
> -static void __of_free_phandle_cache(void)
> +static struct device_node** __of_free_phandle_cache(void)
>  {
> u32 cache_entries = phandle_cache_mask + 1;
> u32 k;
> +   struct device_node **shadow;
>
> if (!phandle_cache)
> -   return;
> +   return NULL;
>
> for (k = 0; k < cache_entries; k++)
> of_node_put(phandle_cache[k]);
>
> shadow = phandle_cache;
> phandle_cache = NULL;
> +   return shadow;
>  }
>
>  int of_free_phandle_cache(void)
>  {
> unsigned long flags;
> +   struct device_node **shadow;
>
> raw_spin_lock_irqsave(_lock, flags);
>
> -   __of_free_phandle_cache();
> +   shadow = __of_free_phandle_cache();
>
> raw_spin_unlock_irqrestore(_lock, flags);
> -
> +   kfree(shadow);
> return 0;
>  }
>  #if !defined(CONFIG_MODULES)
> @@ -169,27 +172,24 @@ void of_populate_phandle_cache(void)
>
> raw_spin_lock_irqsave(_lock, flags);
>
> -   __of_free_phandle_cache();
> +   shadow = __of_free_phandle_cache();
>
> for_each_of_allnodes(np)
> if (np->phandle && np->phandle != OF_PHANDLE_ILLEGAL)
> phandles++;
>
> -   raw_spin_unlock_irqrestore(_lock, flags);
> -   kfree(shadow);
> -
> if (!phandles)
> -   return;
> +   goto out;
> +   raw_spin_unlock_irqrestore(_lock, flags);
>
> cache_entries = roundup_pow_of_two(phandles);
> phandle_cache_mask = cache_entries - 1;
>
> -   shadow = kcalloc(cache_entries, sizeof(*phandle_cache), GFP_KERNEL);
> -
> -   if (!shadow)
> -   return;
> +   phandle_cache = kcalloc(cache_entries, sizeof(*phandle_cache),
> +   GFP_ATOMIC);
> raw_spin_lock_irqsave(_lock, flags);
> -   phandle_cache = shadow;
> +   if (!phandle_cache)
> +   goto out;
>
> for_each_of_allnodes(np)
> if (np->phandle && np->phandle != OF_PHANDLE_ILLEGAL) {
> @@ -197,7 +197,9 @@ void of_populate_phandle_cache(void)
> phandle_cache[np->phandle & phandle_cache_mask] = np;
> }
>
> +out:
> raw_spin_unlock_irqrestore(_lock, flags);
> +   kfree(shadow);
>  }
>
>  void __init of_core_init(void)
> --
> 2.7.4
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] v4.18.x - stable updates comprising v4.18.32

2019-03-21 Thread Paul Gortmaker 
Bruce, Yocto kernel folks:

Here is the next 4.18.x stable update "extension" primarily created
for the Yocto project, continuing from the previous v4.18.30 release.

There are about 165 commits here, based on commits chosen from what
were used in the existing 4.19.29 --> 4.19.30 stable releases.
Nothing unusual to report in this release, just the routine sort of
stable type commits once again.  Which is a good thing!

I've put this 4.18.x queue through the usual testing; build testing
on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis
and finally some sanity runtime tests on x86-64.

I did the signed tag just as per the previously released versions.
Please find a signed v4.18.32 tag using this key:

http://pgp.mit.edu/pks/lookup?op=vindex=0xEBCE84042C07D1D6

in the repo in the kernel.org directory here:

   https://git.kernel.org/cgit/linux/kernel/git/paulg/linux-4.18.y.git/
   git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-4.18.y.git

for merge to standard/base in linux-yocto-4.18 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

   https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-4.18.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 4.18.x release.

Paul.
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[linux-yocto] [PATCH 4.18-rt] of: phandle_cache merge fixup for preempt-rt

2019-03-21 Thread Paul Gortmaker 
In yocto merge 5cc3fddf0e2a ("Merge branch 'v4.18/standard/base' into
v4.18/standard/preempt-rt/base") there was a conflict between the
backport of upstream b8a9ac1a5b99 ("of: of_node_get()/of_node_put() nodes
held in phandle cache") and the rt-specific commit b75caf08b721 ("of:
allocate / free phandle cache outside of the devtree_lock")

Unfortunately the conflict resolution left a shadow variable introduced
by the rt patch as undefined, resulting in:

drivers/of/base.c:120:2: error: 'shadow' undeclared (first use in this function)
  shadow = phandle_cache;
  ^~

drivers/of/base.c: In function 'of_populate_phandle_cache':
drivers/of/base.c:182:7: warning: 'shadow' is used uninitialized in this 
function [-Wuninitialized]

Here we create a merge fix-up that basically aligns the impacted code to
match what is currently found in the 4.19-rt (as of v4.19.15-rt12).

Reported-by: Yue Tao 
Signed-off-by: Paul Gortmaker 

diff --git a/drivers/of/base.c b/drivers/of/base.c
index 904c7686f9d7..4a33ef482bcc 100644
--- a/drivers/of/base.c
+++ b/drivers/of/base.c
@@ -106,31 +106,34 @@ static u32 phandle_cache_mask;
 /*
  * Caller must hold devtree_lock.
  */
-static void __of_free_phandle_cache(void)
+static struct device_node** __of_free_phandle_cache(void)
 {
u32 cache_entries = phandle_cache_mask + 1;
u32 k;
+   struct device_node **shadow;
 
if (!phandle_cache)
-   return;
+   return NULL;
 
for (k = 0; k < cache_entries; k++)
of_node_put(phandle_cache[k]);
 
shadow = phandle_cache;
phandle_cache = NULL;
+   return shadow;
 }
 
 int of_free_phandle_cache(void)
 {
unsigned long flags;
+   struct device_node **shadow;
 
raw_spin_lock_irqsave(_lock, flags);
 
-   __of_free_phandle_cache();
+   shadow = __of_free_phandle_cache();
 
raw_spin_unlock_irqrestore(_lock, flags);
-
+   kfree(shadow);
return 0;
 }
 #if !defined(CONFIG_MODULES)
@@ -169,27 +172,24 @@ void of_populate_phandle_cache(void)
 
raw_spin_lock_irqsave(_lock, flags);
 
-   __of_free_phandle_cache();
+   shadow = __of_free_phandle_cache();
 
for_each_of_allnodes(np)
if (np->phandle && np->phandle != OF_PHANDLE_ILLEGAL)
phandles++;
 
-   raw_spin_unlock_irqrestore(_lock, flags);
-   kfree(shadow);
-
if (!phandles)
-   return;
+   goto out;
+   raw_spin_unlock_irqrestore(_lock, flags);
 
cache_entries = roundup_pow_of_two(phandles);
phandle_cache_mask = cache_entries - 1;
 
-   shadow = kcalloc(cache_entries, sizeof(*phandle_cache), GFP_KERNEL);
-
-   if (!shadow)
-   return;
+   phandle_cache = kcalloc(cache_entries, sizeof(*phandle_cache),
+   GFP_ATOMIC);
raw_spin_lock_irqsave(_lock, flags);
-   phandle_cache = shadow;
+   if (!phandle_cache)
+   goto out;
 
for_each_of_allnodes(np)
if (np->phandle && np->phandle != OF_PHANDLE_ILLEGAL) {
@@ -197,7 +197,9 @@ void of_populate_phandle_cache(void)
phandle_cache[np->phandle & phandle_cache_mask] = np;
}
 
+out:
raw_spin_unlock_irqrestore(_lock, flags);
+   kfree(shadow);
 }
 
 void __init of_core_init(void)
-- 
2.7.4

-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] [meta-security][PATCH] ibmswtpm2: Add new recipe

2019-03-21 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 .../recipes-tpm2/ibmswtpm2/ibmswtpm2_1332.bb  | 24 +++
 1 file changed, 24 insertions(+)
 create mode 100644 meta-tpm/recipes-tpm2/ibmswtpm2/ibmswtpm2_1332.bb

diff --git a/meta-tpm/recipes-tpm2/ibmswtpm2/ibmswtpm2_1332.bb 
b/meta-tpm/recipes-tpm2/ibmswtpm2/ibmswtpm2_1332.bb
new file mode 100644
index 000..a6068e6
--- /dev/null
+++ b/meta-tpm/recipes-tpm2/ibmswtpm2/ibmswtpm2_1332.bb
@@ -0,0 +1,24 @@
+SUMMARY = "IBM's Software TPM 2.0"
+
+LICENSE = "BSD"
+SECTION = "securty/tpm"
+LIC_FILES_CHKSUM = "file://../LICENSE;md5=1e023f61454ac828b4aa1bc4293f7d5f"
+
+SRC_URI = "https://sourceforge.net/projects/ibmswtpm2/files/ibmtpm1332.tar.gz;
+SRC_URI[md5sum] = "0ab34a655b4e09812d7ada19746af4f9"
+SRC_URI[sha256sum] = 
"8e8193af3d11d9ff6a951dda8cd1f4693cb01934a8ad7876b84e92c6148ab0fd"
+
+DEPENDS = "openssl"
+
+S = "${WORKDIR}/src"
+
+LDFLAGS = "${LDFALGS}"
+
+do_compile () {
+   make CC='${CC}'
+}
+
+do_install () {
+   install -d ${D}/${bindir}
+   install -m 0755 tpm_server  ${D}/${bindir}
+}
-- 
2.17.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Thud: building SDK fails: cannot find -lssp

2019-03-21 Thread Mark Hatle 
On 3/20/19 5:30 PM, Lukasz Zemla wrote:
> Hello All,
> 
> I am trying to build SDK using Yocto thud tagged 2.6.1. Toolchain from 
> meta-linaro (edb7ffc2a121df7596385595abe75180296103e0). Unfortunately it 
> fails during perl build, complaining about missing ssp_nonshared and ssp 
> libraries. 

The ssp component comes from the toolchain.  If you can reproduce this on the
base system (not meta-linaro toolchain), then it may be a broader bug.
Otherwise, it's likely related to either a bug or configuration decision in
meta-linaro.

--Mark

> Do you have any ideas how to fix it? 
> I know it is about stack smash protector, but shouldn't it be automatically 
> included and available for linker during a build?
> 
> 
> | x86_64-pokysdk-linux-gcc  
> --sysroot=/data/home/user/00-projects/proj_myproj_system0/build_myproj_system0/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-perl/5.24.4-r0/recipe-sysroot
>  -Wl,-O1 -fstack-protector -o miniperl \
> | opmini.o perlmini.o  gv.o toke.o perly.o pad.o regcomp.o dump.o util.o 
> mg.o reentr.o mro_core.o keywords.o hv.o av.o run.o pp_hot.o sv.o pp.o 
> scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o 
> universal.o globals.o perlio.o perlapi.o numeric.o mathoms.o locale.o 
> pp_pack.o pp_sort.o caretx.o dquote.o time64.o  miniperlmain.o  -lpthread  
> -ldl -lm -lcrypt -lutil -lc
> | 
> /data/home/user/00-projects/proj_myproj_system0/build_myproj_system0/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-perl/5.24.4-r0/recipe-sysroot-native/usr/bin/x86_64-pokysdk-linux/../../libexec/x86_64-pokysdk-linux/gcc/x86_64-pokysdk-linux/7.1.1/ld:
>  cannot find -lssp_nonshared
> | 
> /data/home/user/00-projects/proj_myproj_system0/build_myproj_system0/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-perl/5.24.4-r0/recipe-sysroot-native/usr/bin/x86_64-pokysdk-linux/../../libexec/x86_64-pokysdk-linux/gcc/x86_64-pokysdk-linux/7.1.1/ld:
>  cannot find -lssp
> | collect2: error: ld returned 1 exit status
> | makefile:391: recipe for target 'lib/buildcustomize.pl' failed
> | make[1]: *** [lib/buildcustomize.pl] Error 1
> | make[1]: Leaving directory 
> '/data/home/user/00-projects/proj_myproj_system0/build_myproj_system0/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-perl/5.24.4-r0/perl-5.24.4'
> | make[1]: Entering directory 
> '/data/home/user/00-projects/proj_myproj_system0/build_myproj_system0/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-perl/5.24.4-r0/perl-5.24.4'
> | ./miniperl -Ilib autodoc.pl
> | make[1]: ./miniperl: Command not found
> | makefile:441: recipe for target 'pod/perlintern.pod' failed
> 
> Thank you in advance,
> Lukasz
> 
> ***
> The information in this email is confidential and intended solely for the 
> individual or entity to whom it is addressed.  If you have received this 
> email in error please notify the sender by return e-mail, delete this email, 
> and refrain from any disclosure or action based on the information.
> ***
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto