All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: What is expected of a kernel recipe nowadays?
Date: Mon, 5 Jan 2015 09:29:58 +0100	[thread overview]
Message-ID: <54AA4B86.9040905@topic.nl> (raw)
In-Reply-To: <54AA4536.7030101@topic.nl>

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.looijmans@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.looijmans@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/



  reply	other threads:[~2015-01-05  8:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05  8:03 What is expected of a kernel recipe nowadays? Mike Looijmans
2015-01-05  8:29 ` Mike Looijmans [this message]
2015-01-05 20:18   ` Bruce Ashfield
2015-01-06  0:47     ` Otavio Salvador
2015-01-06  7:14     ` Mike Looijmans
2015-01-06  8:57       ` Martin Jansa
2015-01-06 11:04         ` Martin Jansa
2015-01-06 11:04           ` [OE-core] " Martin Jansa
2015-01-06 11:33           ` Burton, Ross
2015-01-06 11:33             ` [OE-core] " Burton, Ross
2015-01-06 14:08             ` Bruce Ashfield
2015-01-06 14:08               ` [OE-core] " Bruce Ashfield
2015-01-06 11:08         ` Burton, Ross
2015-01-07 10:07           ` Martin Jansa
2015-01-07 13:08             ` Bruce Ashfield
2015-01-07 15:48             ` Bruce Ashfield
2015-01-07 15:56               ` Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54AA4B86.9040905@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.