Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-07 Thread Martin Jansa 
On Tue, Jan 06, 2015 at 11:08:53AM +, Burton, Ross wrote:
 On 6 January 2015 at 08:57, Martin Jansa martin.ja...@gmail.com wrote:
 
  2) do_configure failing:
 
  ERROR: Function failed: do_configure (log file is located at
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  ERROR: Logfile of failure stored in:
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
  Log data follows:
  | DEBUG: Executing python function sysroot_cleansstate
  | DEBUG: Python function sysroot_cleansstate finished
  | DEBUG: Executing shell function do_configure
  | NOTE: make oldconfig
  | make: *** No rule to make target `oldconfig'.  Stop.
  | ERROR: oe_runmake failed
  | WARNING: exit code 1 from a shell command.
  | ERROR: Function failed: do_configure (log file is located at
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
  do_configure: Failed
  ERROR: Task 491
  (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/
  linux-lg-mako_git.bb, do_configure) failed with exit code '1'
 
 
 I'll Me Too here, often hitting this on rebuilds:
 
 DEBUG: Executing shell function do_configure
 NOTE: make -C /data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel
 O=/data/poky-master/tmp/work/qemuarm64-poky-linux/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_902f34d361-r0/linux-qemuarm64-standard-build
 oldnoconfig
 make: Entering directory
 `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel'
 make: *** No rule to make target `oldnoconfig'.  Stop.
 make: Leaving directory
 `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel' ERROR: Task 77
 (/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
 do_configure) failed with exit code '1'

last world build revealed new kind of error:

both qemux86 and qemux86-64 failed like this

ERROR: Function failed: do_kernel_configme (log file is located at 
/home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
ERROR: Logfile of failure stored in: 
/home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974
Log data follows:
| DEBUG: Executing shell function do_kernel_configme
| NOTE: kernel configme
| [INFO] Configuring target/machine combo: standard/qemux86-64
| [INFO] collecting configs in .meta/meta-series
| ERROR: could not sanitize configuration fragments
|errors are logged in 
/home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemux86-64/usr/src/kernel/.meta/cfg/standard/common-pc-64/config.log
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_configme (log file is located at 
/home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
NOTE: recipe linux-yocto-3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0: task 
do_kernel_configme: Failed

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-07 Thread Bruce Ashfield 
On Wed, Jan 7, 2015 at 5:07 AM, Martin Jansa martin.ja...@gmail.com wrote:
 On Tue, Jan 06, 2015 at 11:08:53AM +, Burton, Ross wrote:
 On 6 January 2015 at 08:57, Martin Jansa martin.ja...@gmail.com wrote:

  2) do_configure failing:
 
  ERROR: Function failed: do_configure (log file is located at
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  ERROR: Logfile of failure stored in:
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
  Log data follows:
  | DEBUG: Executing python function sysroot_cleansstate
  | DEBUG: Python function sysroot_cleansstate finished
  | DEBUG: Executing shell function do_configure
  | NOTE: make oldconfig
  | make: *** No rule to make target `oldconfig'.  Stop.
  | ERROR: oe_runmake failed
  | WARNING: exit code 1 from a shell command.
  | ERROR: Function failed: do_configure (log file is located at
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
  do_configure: Failed
  ERROR: Task 491
  (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/
  linux-lg-mako_git.bb, do_configure) failed with exit code '1'
 

 I'll Me Too here, often hitting this on rebuilds:

 DEBUG: Executing shell function do_configure
 NOTE: make -C /data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel
 O=/data/poky-master/tmp/work/qemuarm64-poky-linux/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_902f34d361-r0/linux-qemuarm64-standard-build
 oldnoconfig
 make: Entering directory
 `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel'
 make: *** No rule to make target `oldnoconfig'.  Stop.
 make: Leaving directory
 `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel' ERROR: Task 77
 (/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
 do_configure) failed with exit code '1'

 last world build revealed new kind of error:

 both qemux86 and qemux86-64 failed like this

 ERROR: Function failed: do_kernel_configme (log file is located at 
 /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
 ERROR: Logfile of failure stored in: 
 /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974
 Log data follows:
 | DEBUG: Executing shell function do_kernel_configme
 | NOTE: kernel configme
 | [INFO] Configuring target/machine combo: standard/qemux86-64
 | [INFO] collecting configs in .meta/meta-series
 | ERROR: could not sanitize configuration fragments
 |errors are logged in 
 /home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemux86-64/usr/src/kernel/.meta/cfg/standard/common-pc-64/config.log
 | WARNING: exit code 1 from a shell command.
 | ERROR: Function failed: do_kernel_configme (log file is located at 
 /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
 NOTE: recipe linux-yocto-3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0: task 
 do_kernel_configme: Failed

I have a fix for this one. I'll open a tracking case when I'm into the office.

Bruce


 --
 Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com

 --
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.openembedded.org/mailman/listinfo/openembedded-core




-- 
Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-07 Thread Martin Jansa 
On Wed, Jan 07, 2015 at 10:48:50AM -0500, Bruce Ashfield wrote:
 On Wed, Jan 7, 2015 at 5:07 AM, Martin Jansa martin.ja...@gmail.com wrote:
  On Tue, Jan 06, 2015 at 11:08:53AM +, Burton, Ross wrote:
  On 6 January 2015 at 08:57, Martin Jansa martin.ja...@gmail.com wrote:
 
   2) do_configure failing:
  
   ERROR: Function failed: do_configure (log file is located at
   /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
   ERROR: Logfile of failure stored in:
   /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
   Log data follows:
   | DEBUG: Executing python function sysroot_cleansstate
   | DEBUG: Python function sysroot_cleansstate finished
   | DEBUG: Executing shell function do_configure
   | NOTE: make oldconfig
   | make: *** No rule to make target `oldconfig'.  Stop.
   | ERROR: oe_runmake failed
   | WARNING: exit code 1 from a shell command.
   | ERROR: Function failed: do_configure (log file is located at
   /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
   NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
   do_configure: Failed
   ERROR: Task 491
   (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/
   linux-lg-mako_git.bb, do_configure) failed with exit code '1'
  
 
  I'll Me Too here, often hitting this on rebuilds:
 
  DEBUG: Executing shell function do_configure
  NOTE: make -C /data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel
  O=/data/poky-master/tmp/work/qemuarm64-poky-linux/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_902f34d361-r0/linux-qemuarm64-standard-build
  oldnoconfig
  make: Entering directory
  `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel'
  make: *** No rule to make target `oldnoconfig'.  Stop.
  make: Leaving directory
  `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel' ERROR: Task 77
  (/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
  do_configure) failed with exit code '1'
 
  last world build revealed new kind of error:
 
  both qemux86 and qemux86-64 failed like this
 
  ERROR: Function failed: do_kernel_configme (log file is located at 
  /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
  ERROR: Logfile of failure stored in: 
  /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974
  Log data follows:
  | DEBUG: Executing shell function do_kernel_configme
  | NOTE: kernel configme
  | [INFO] Configuring target/machine combo: standard/qemux86-64
  | [INFO] collecting configs in .meta/meta-series
  | ERROR: could not sanitize configuration fragments
  |errors are logged in 
  /home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemux86-64/usr/src/kernel/.meta/cfg/standard/common-pc-64/config.log
  | WARNING: exit code 1 from a shell command.
  | ERROR: Function failed: do_kernel_configme (log file is located at 
  /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
  NOTE: recipe linux-yocto-3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0: task 
  do_kernel_configme: Failed
 
 I spoke to soon before. Where can I find the config that triggered this ? I 
 just
 built the latest master and my fragments/patches were all properly applied in
 the default build:

It's random, the same oe-core revision first built it fine, then it
failed, then it again built fine, see:
http://www.openembedded.org/wiki/Bitbake_World_Status
the successful build isn't there yet, but rebuilding from the same
sstate finished kernel fine

 -
 
 DEBUG: Executing shell function do_kernel_configme
 NOTE: kernel configme
 [INFO] Configuring target/machine combo: standard/qemux86-64
 [INFO] collecting configs in .meta/meta-series
 [INFO] Pre-processed cfg file qemux86-64-standard-config-3.17.6 created.
 [INFO] processing of raw cfg data completed.
 
 
   Configuration stored in
 /home/bruce/oe/build/tmp/work/qemux86_64-poky-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/linux-qemux86_64-standard-build/.config
 
 
   To build with this kernel configuration, ensure a suitable toolchain
   is in your path for x86_64, note its common command prefix, and do:
 
make

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-07 Thread Bruce Ashfield 
On Wed, Jan 7, 2015 at 5:07 AM, Martin Jansa martin.ja...@gmail.com wrote:
 On Tue, Jan 06, 2015 at 11:08:53AM +, Burton, Ross wrote:
 On 6 January 2015 at 08:57, Martin Jansa martin.ja...@gmail.com wrote:

  2) do_configure failing:
 
  ERROR: Function failed: do_configure (log file is located at
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  ERROR: Logfile of failure stored in:
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
  Log data follows:
  | DEBUG: Executing python function sysroot_cleansstate
  | DEBUG: Python function sysroot_cleansstate finished
  | DEBUG: Executing shell function do_configure
  | NOTE: make oldconfig
  | make: *** No rule to make target `oldconfig'.  Stop.
  | ERROR: oe_runmake failed
  | WARNING: exit code 1 from a shell command.
  | ERROR: Function failed: do_configure (log file is located at
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
  do_configure: Failed
  ERROR: Task 491
  (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/
  linux-lg-mako_git.bb, do_configure) failed with exit code '1'
 

 I'll Me Too here, often hitting this on rebuilds:

 DEBUG: Executing shell function do_configure
 NOTE: make -C /data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel
 O=/data/poky-master/tmp/work/qemuarm64-poky-linux/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_902f34d361-r0/linux-qemuarm64-standard-build
 oldnoconfig
 make: Entering directory
 `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel'
 make: *** No rule to make target `oldnoconfig'.  Stop.
 make: Leaving directory
 `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel' ERROR: Task 77
 (/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
 do_configure) failed with exit code '1'

 last world build revealed new kind of error:

 both qemux86 and qemux86-64 failed like this

 ERROR: Function failed: do_kernel_configme (log file is located at 
 /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
 ERROR: Logfile of failure stored in: 
 /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974
 Log data follows:
 | DEBUG: Executing shell function do_kernel_configme
 | NOTE: kernel configme
 | [INFO] Configuring target/machine combo: standard/qemux86-64
 | [INFO] collecting configs in .meta/meta-series
 | ERROR: could not sanitize configuration fragments
 |errors are logged in 
 /home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemux86-64/usr/src/kernel/.meta/cfg/standard/common-pc-64/config.log
 | WARNING: exit code 1 from a shell command.
 | ERROR: Function failed: do_kernel_configme (log file is located at 
 /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
 NOTE: recipe linux-yocto-3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0: task 
 do_kernel_configme: Failed

I spoke to soon before. Where can I find the config that triggered this ? I just
built the latest master and my fragments/patches were all properly applied in
the default build:

-

DEBUG: Executing shell function do_kernel_configme
NOTE: kernel configme
[INFO] Configuring target/machine combo: standard/qemux86-64
[INFO] collecting configs in .meta/meta-series
[INFO] Pre-processed cfg file qemux86-64-standard-config-3.17.6 created.
[INFO] processing of raw cfg data completed.


  Configuration stored in
/home/bruce/oe/build/tmp/work/qemux86_64-poky-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/linux-qemux86_64-standard-build/.config


  To build with this kernel configuration, ensure a suitable toolchain
  is in your path for x86_64, note its common command prefix, and do:

   make 
O=/home/bruce/oe/build/tmp/work/qemux86_64-poky-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/linux-qemux86_64-standard-build
ARCH=x86_64 \
CROSS_COMPILE=cross-compile-prefix

DEBUG: Shell function do_kernel_configme finished

-

Bruce


 --
 Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com

 --
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-06 Thread Martin Jansa 
On Tue, Jan 06, 2015 at 08:14:33AM +0100, Mike Looijmans wrote:
 On 01/05/2015 09:18 PM, Bruce Ashfield wrote:
  On Mon, Jan 5, 2015 at 3:29 AM, Mike Looijmans mike.looijm...@topic.nl 
  wrote:
  I think I found it. The kernel bbclass changes S to point elsewhere.
  Moving the statement
  S = ${WORKDIR}/git
  to after the inherit kernel line makes the compile run again.
 
 
  Interesting. Can you confirm that Richard's commit:
 
  -
 
  commit 1dd37a2a9960ad26e27567d1871d78bec336e1a2
  Author: Richard Purdie richard.pur...@linuxfoundation.org
  Date:   Fri Dec 19 17:46:27 2014 +
 
   kernel: Fix non linux-yocto builds
 
   After the recent kernel changes, non linux-yocto builds stopped working
   properly for two reasons:
 
   a) ${S} was being reset to ${WORKDIR}/git for example and 
  STAGING_KERNEL_DIR
  did not contain the source
 
   b) Most builds were using ${B} == ${S}
 
   This patch adds a fixup to the unpack function to handle the case where
   ${S} != ${STAGING_KERNEL_DIR} and also set up the infrastrcture so that
   B != S for kernel builds from now on. The kernel build system is one 
  of the
   best for supporting this and there is no good reason not to take 
  advantage
   of it.
 
   (From OE-Core rev: 106dab2fd0321e6b4e77b40111e59a3a31d329d4)
 
   Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
 
  
 
  Is in your tree ? it should be fixing things up and allowing the source to
  be found.
 
 Yes, this is the part that changes S and it's how I discovered to move the 
 assignment to after inheriting it.
 
 
  Alternatively, if you drop the explicit set of S, does the build start 
  working
  again ?
 
 If I just remove the S=... line, it fails in the same way. The git fetch 
 apparently places the code at WORKDIR/git where the new kernel recipe cannot 
 find it.

FWIW: I'm also seeing various kernel failures since the changes.

Most my kernel are also using linux.inc from meta-oe which wasn't updated yet
(I plan to look into it soon, unless someone else beats me to it)

The worst part is that some of these issues are random (the race-condition 
showing
more often than before).

1) do_unpack failing:

ERROR: Error executing a python function in 
/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-samsung/recipes-kernel/linux/linux-samsung-tuna_git.bb:

The stack trace of python calls that resulted in this exception/failure was:
File: 'base_do_unpack', lineno: 24, function: module
 0020:subprocess.call(d.expand(mv 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/maguro-webos-linux-gnueabi/linux-samsung-tuna/3_3.0.72+gitrAUTOINC+f8ed73f94a-r12/git/
 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/sysroots/maguro/usr/src/kernel),
 shell=True)
 0021:os.symlink(kernsrc, s)
 0022:
 0023:
 *** 0024:base_do_unpack(d)
 0025:
File: 'base_do_unpack', lineno: 21, function: base_do_unpack
 0017:bb.utils.mkdirhier(kernsrc)
 0018:bb.utils.remove(kernsrc, recurse=True)
 0019:import subprocess
 0020:subprocess.call(d.expand(mv 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/maguro-webos-linux-gnueabi/linux-samsung-tuna/3_3.0.72+gitrAUTOINC+f8ed73f94a-r12/git/
 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/sysroots/maguro/usr/src/kernel),
 shell=True)
 *** 0021:os.symlink(kernsrc, s)
 0022:
 0023:
 0024:base_do_unpack(d)
 0025:
Exception: OSError: [Errno 2] No such file or directory

ERROR: Function failed: base_do_unpack
ERROR: Logfile of failure stored in: 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/maguro-webos-linux-gnueabi/linux-samsung-tuna/3_3.0.72+gitrAUTOINC+f8ed73f94a-r12/temp/log.do_unpack.13495

2) do_configure failing:

ERROR: Function failed: do_configure (log file is located at 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
ERROR: Logfile of failure stored in: 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make oldconfig
| make: *** No rule to make target `oldconfig'.  Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at 
/home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task do_configure:

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-06 Thread Martin Jansa 
On Tue, Jan 06, 2015 at 09:57:31AM +0100, Martin Jansa wrote:
 FWIW: I'm also seeing various kernel failures since the changes.
 
 Most my kernel are also using linux.inc from meta-oe which wasn't updated yet
 (I plan to look into it soon, unless someone else beats me to it)
 
 The worst part is that some of these issues are random (the race-condition 
 showing
 more often than before).
 
 1) do_unpack failing:
 
 ERROR: Error executing a python function in 
 /home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-samsung/recipes-kernel/linux/linux-samsung-tuna_git.bb:
 File: 'base_do_unpack', lineno: 21, function: base_do_unpack
  0017:bb.utils.mkdirhier(kernsrc)
  0018:bb.utils.remove(kernsrc, recurse=True)
  0019:import subprocess
  0020:subprocess.call(d.expand(mv 
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/maguro-webos-linux-gnueabi/linux-samsung-tuna/3_3.0.72+gitrAUTOINC+f8ed73f94a-r12/git/
  
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/sysroots/maguro/usr/src/kernel),
  shell=True)
  *** 0021:os.symlink(kernsrc, s)
  0022:
  0023:
  0024:base_do_unpack(d)
  0025:
 Exception: OSError: [Errno 2] No such file or directory

This fails when S ends with slash, fix in
http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/master

 2) do_configure failing:
 
 ERROR: Function failed: do_configure (log file is located at 
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
 ERROR: Logfile of failure stored in: 
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
 Log data follows:
 | DEBUG: Executing python function sysroot_cleansstate
 | DEBUG: Python function sysroot_cleansstate finished
 | DEBUG: Executing shell function do_configure
 | NOTE: make oldconfig
 | make: *** No rule to make target `oldconfig'.  Stop.
 | ERROR: oe_runmake failed
 | WARNING: exit code 1 from a shell command.
 | ERROR: Function failed: do_configure (log file is located at 
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
 NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task 
 do_configure: Failed
 ERROR: Task 491 
 (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/linux-lg-mako_git.bb,
  do_configure) failed with exit code '1'

This was caused by linux.inc, fixed in:
http://lists.openembedded.org/pipermail/openembedded-devel/2015-January/099687.html

 3) do_patch failing when S assignment is dropped

This isn't relevant, S assignment is still needed

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-06 Thread Burton, Ross 
On 6 January 2015 at 08:57, Martin Jansa martin.ja...@gmail.com wrote:

 2) do_configure failing:

 ERROR: Function failed: do_configure (log file is located at
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
 ERROR: Logfile of failure stored in:
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
 Log data follows:
 | DEBUG: Executing python function sysroot_cleansstate
 | DEBUG: Python function sysroot_cleansstate finished
 | DEBUG: Executing shell function do_configure
 | NOTE: make oldconfig
 | make: *** No rule to make target `oldconfig'.  Stop.
 | ERROR: oe_runmake failed
 | WARNING: exit code 1 from a shell command.
 | ERROR: Function failed: do_configure (log file is located at
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
 NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
 do_configure: Failed
 ERROR: Task 491
 (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/
 linux-lg-mako_git.bb, do_configure) failed with exit code '1'


I'll Me Too here, often hitting this on rebuilds:

DEBUG: Executing shell function do_configure
NOTE: make -C /data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel
O=/data/poky-master/tmp/work/qemuarm64-poky-linux/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_902f34d361-r0/linux-qemuarm64-standard-build
oldnoconfig
make: Entering directory
`/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel'
make: *** No rule to make target `oldnoconfig'.  Stop.
make: Leaving directory
`/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel' ERROR: Task 77
(/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
do_configure) failed with exit code '1'

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-06 Thread Burton, Ross 
On 6 January 2015 at 11:04, Martin Jansa martin.ja...@gmail.com wrote:

  | make: *** No rule to make target `oldconfig'.  Stop.
  | ERROR: oe_runmake failed
  | WARNING: exit code 1 from a shell command.
  | ERROR: Function failed: do_configure (log file is located at
 /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
 do_configure: Failed
  ERROR: Task 491
 (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/
 linux-lg-mako_git.bb, do_configure) failed with exit code '1'

 This was caused by linux.inc, fixed in:

 http://lists.openembedded.org/pipermail/openembedded-devel/2015-January/099687.html


I'm replicating this error with an oe-core kernel, so there's more causes
here.

Ross
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-06 Thread Bruce Ashfield 
On Tue, Jan 6, 2015 at 6:33 AM, Burton, Ross ross.bur...@intel.com wrote:

 On 6 January 2015 at 11:04, Martin Jansa martin.ja...@gmail.com wrote:

  | make: *** No rule to make target `oldconfig'.  Stop.
  | ERROR: oe_runmake failed
  | WARNING: exit code 1 from a shell command.
  | ERROR: Function failed: do_configure (log file is located at
  /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
  NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
  do_configure: Failed
  ERROR: Task 491
  (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/linux-lg-mako_git.bb,
  do_configure) failed with exit code '1'

 This was caused by linux.inc, fixed in:

 http://lists.openembedded.org/pipermail/openembedded-devel/2015-January/099687.html


 I'm replicating this error with an oe-core kernel, so there's more causes
 here.

Can you log the replicating steps and point me at the bug ? I can take any fixes
from there.

Bruce


 Ross

 --
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.openembedded.org/mailman/listinfo/openembedded-core




-- 
Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-05 Thread Mike Looijmans 

On 01/05/2015 09:18 PM, Bruce Ashfield wrote:

On Mon, Jan 5, 2015 at 3:29 AM, Mike Looijmans mike.looijm...@topic.nl wrote:

I think I found it. The kernel bbclass changes S to point elsewhere.
Moving the statement
S = ${WORKDIR}/git
to after the inherit kernel line makes the compile run again.



Interesting. Can you confirm that Richard's commit:

-

commit 1dd37a2a9960ad26e27567d1871d78bec336e1a2
Author: Richard Purdie richard.pur...@linuxfoundation.org
Date:   Fri Dec 19 17:46:27 2014 +

 kernel: Fix non linux-yocto builds

 After the recent kernel changes, non linux-yocto builds stopped working
 properly for two reasons:

 a) ${S} was being reset to ${WORKDIR}/git for example and 
STAGING_KERNEL_DIR
did not contain the source

 b) Most builds were using ${B} == ${S}

 This patch adds a fixup to the unpack function to handle the case where
 ${S} != ${STAGING_KERNEL_DIR} and also set up the infrastrcture so that
 B != S for kernel builds from now on. The kernel build system is one of the
 best for supporting this and there is no good reason not to take advantage
 of it.

 (From OE-Core rev: 106dab2fd0321e6b4e77b40111e59a3a31d329d4)

 Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org



Is in your tree ? it should be fixing things up and allowing the source to
be found.


Yes, this is the part that changes S and it's how I discovered to move the 
assignment to after inheriting it.




Alternatively, if you drop the explicit set of S, does the build start working
again ?


If I just remove the S=... line, it fails in the same way. The git fetch 
apparently places the code at WORKDIR/git where the new kernel recipe cannot 
find it.





Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijm...@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] What is expected of a kernel recipe nowadays?

2015-01-05 Thread Mike Looijmans 
I updated to the current master of OE-core, but I can't get the kernel recipe 
to work any longer:

https://github.com/topic-embedded-products/meta-topic/blob/master/recipes-kernel/linux-zynq/linux-topic.bb

(I got similar problems in other projects too, I'm focussing on this one first.)

Several things were changed in kernel.bbclass, but I don't understand what is 
being expected from me now to get the kernel recipe in working order again.



| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make -C 
/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel 
O=/home/mike/zynq_platform/build/tmp-glibc/work/topic_miami_vice-oe-linux-gnueabi/linux-topic/3.17+gitAUTOINC+0feb6e4839-r0/build 
oldnoconfig
| make: Entering directory 
`/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel'

| make: *** No rule to make target `oldnoconfig'.  Stop.
| make: Leaving directory 
`/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel'
| NOTE: make -C 
/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel 
O=/home/mike/zynq_platform/build/tmp-glibc/work/topic_miami_vice-oe-linux-gnueabi/linux-topic/3.17+gitAUTOINC+0feb6e4839-r0/build 
oldconfig




Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijm...@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-05 Thread Mike Looijmans 
I think I found it. The kernel bbclass changes S to point elsewhere. Moving 
the statement

S = ${WORKDIR}/git
to after the inherit kernel line makes the compile run again.



On 01/05/2015 09:03 AM, Mike Looijmans wrote:

I updated to the current master of OE-core, but I can't get the kernel recipe
to work any longer:
https://github.com/topic-embedded-products/meta-topic/blob/master/recipes-kernel/linux-zynq/linux-topic.bb


(I got similar problems in other projects too, I'm focussing on this one first.)

Several things were changed in kernel.bbclass, but I don't understand what is
being expected from me now to get the kernel recipe in working order again.


| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make -C
/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel
O=/home/mike/zynq_platform/build/tmp-glibc/work/topic_miami_vice-oe-linux-gnueabi/linux-topic/3.17+gitAUTOINC+0feb6e4839-r0/build
oldnoconfig
| make: Entering directory
`/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel'

| make: *** No rule to make target `oldnoconfig'.  Stop.
| make: Leaving directory
`/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel'

| NOTE: make -C
/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel
O=/home/mike/zynq_platform/build/tmp-glibc/work/topic_miami_vice-oe-linux-gnueabi/linux-topic/3.17+gitAUTOINC+0feb6e4839-r0/build
oldconfig



Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijm...@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/





Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijm...@topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-05 Thread Otavio Salvador 
On Mon, Jan 5, 2015 at 6:18 PM, Bruce Ashfield bruce.ashfi...@gmail.com wrote:
 On Mon, Jan 5, 2015 at 3:29 AM, Mike Looijmans mike.looijm...@topic.nl 
 wrote:
 I think I found it. The kernel bbclass changes S to point elsewhere.
 Moving the statement
 S = ${WORKDIR}/git
 to after the inherit kernel line makes the compile run again.

We handled similar failures with:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?id=f69b21d39feca9a4d71d53980fc5c9917ba6c5ac

Take a look if it helps.

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] What is expected of a kernel recipe nowadays?

2015-01-05 Thread Bruce Ashfield 
On Mon, Jan 5, 2015 at 3:29 AM, Mike Looijmans mike.looijm...@topic.nl wrote:
 I think I found it. The kernel bbclass changes S to point elsewhere.
 Moving the statement
 S = ${WORKDIR}/git
 to after the inherit kernel line makes the compile run again.


Interesting. Can you confirm that Richard's commit:

-

commit 1dd37a2a9960ad26e27567d1871d78bec336e1a2
Author: Richard Purdie richard.pur...@linuxfoundation.org
Date:   Fri Dec 19 17:46:27 2014 +

kernel: Fix non linux-yocto builds

After the recent kernel changes, non linux-yocto builds stopped working
properly for two reasons:

a) ${S} was being reset to ${WORKDIR}/git for example and STAGING_KERNEL_DIR
   did not contain the source

b) Most builds were using ${B} == ${S}

This patch adds a fixup to the unpack function to handle the case where
${S} != ${STAGING_KERNEL_DIR} and also set up the infrastrcture so that
B != S for kernel builds from now on. The kernel build system is one of the
best for supporting this and there is no good reason not to take advantage
of it.

(From OE-Core rev: 106dab2fd0321e6b4e77b40111e59a3a31d329d4)

Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org



Is in your tree ? it should be fixing things up and allowing the source to
be found.

Alternatively, if you drop the explicit set of S, does the build start working
again ?

Bruce





 On 01/05/2015 09:03 AM, Mike Looijmans wrote:

 I updated to the current master of OE-core, but I can't get the kernel
 recipe
 to work any longer:

 https://github.com/topic-embedded-products/meta-topic/blob/master/recipes-kernel/linux-zynq/linux-topic.bb


 (I got similar problems in other projects too, I'm focussing on this one
 first.)

 Several things were changed in kernel.bbclass, but I don't understand what
 is
 being expected from me now to get the kernel recipe in working order
 again.


 | DEBUG: Executing python function sysroot_cleansstate
 | DEBUG: Python function sysroot_cleansstate finished
 | DEBUG: Executing shell function do_configure
 | NOTE: make -C

 /home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel

 O=/home/mike/zynq_platform/build/tmp-glibc/work/topic_miami_vice-oe-linux-gnueabi/linux-topic/3.17+gitAUTOINC+0feb6e4839-r0/build
 oldnoconfig
 | make: Entering directory

 `/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel'

 | make: *** No rule to make target `oldnoconfig'.  Stop.
 | make: Leaving directory

 `/home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel'

 | NOTE: make -C

 /home/mike/zynq_platform/build/tmp-glibc/sysroots/topic-miami-vice-xc7z015/usr/src/kernel

 O=/home/mike/zynq_platform/build/tmp-glibc/work/topic_miami_vice-oe-linux-gnueabi/linux-topic/3.17+gitAUTOINC+0feb6e4839-r0/build
 oldconfig



 Met vriendelijke groet / kind regards,

 Mike Looijmans
 System Expert


 TOPIC Embedded Systems
 Eindhovenseweg 32-C, NL-5683 KH Best
 Postbus 440, NL-5680 AK Best
 Telefoon: (+31) (0) 499 33 69 79
 Telefax:  (+31) (0) 499 33 69 70
 E-mail: mike.looijm...@topic.nl
 Website: www.topic.nl

 Please consider the environment before printing this e-mail

 Topic zoekt gedreven (embedded) software specialisten!
 http://topic.nl/vacatures/topic-zoekt-software-engineers/




 Met vriendelijke groet / kind regards,

 Mike Looijmans
 System Expert


 TOPIC Embedded Systems
 Eindhovenseweg 32-C, NL-5683 KH Best
 Postbus 440, NL-5680 AK Best
 Telefoon: (+31) (0) 499 33 69 79
 Telefax:  (+31) (0) 499 33 69 70
 E-mail: mike.looijm...@topic.nl
 Website: www.topic.nl

 Please consider the environment before printing this e-mail

 Topic zoekt gedreven (embedded) software specialisten!
 http://topic.nl/vacatures/topic-zoekt-software-engineers/

 --
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core