public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/7] kernel: fix out of tree module builds
Date: Fri, 19 Dec 2014 12:05:56 +0100	[thread overview]
Message-ID: <lyegrv99wr.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <0247524f2f7ae076fdac8773c3baa0794e5697dd.1418207154.git.bruce.ashfield@windriver.com> (Bruce Ashfield's message of "Wed, 10 Dec 2014 05:34:03 -0500")

Bruce Ashfield <bruce.ashfield-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
writes:

> With the kernel build optimizations, we no longer copy the source from
> the built kernel into the staging dir, since the kernel is unpacked and built
> directly from the staging dir.
>
> This means that a few build artifacts need to be restored to allow out of
> tree modules to once again build.
> ...
> +	
> +	# Copy files required for module builds
> +	cp System.map $kerneldir/System.map-${KERNEL_VERSION}
> +	cp Module.symvers $kerneldir/
> +	cp .config $kerneldir/

This and the following lines seem to void the whole idea of the patchset
because it means that only one kernel can be built.  In our usecase we
build usually two kernels: a full featured one for the main system and a
minimal, initramfs based for a rescue system.

With this change and building both kernels, it is ambiguous which
System.map is used.



Enrico
-- 
SIGMA Chemnitz GmbH       Registergericht:   Amtsgericht Chemnitz HRB 1750
Am Erlenwald 13           Geschaeftsfuehrer: Grit Freitag, Frank Pyritz
09128 Chemnitz


  reply	other threads:[~2014-12-19 11:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 10:34 [PATCH 0/7] kernel: consolidated pull for developer experience Bruce Ashfield
2014-12-10 10:34 ` [PATCH 1/7] kernel: Rearrange for 1.8 Bruce Ashfield
2014-12-10 12:45   ` Bruce Ashfield
2014-12-10 10:34 ` [PATCH 2/7] kernel: fix out of tree module builds Bruce Ashfield
2014-12-19 11:05   ` Enrico Scholz [this message]
2014-12-19 11:51     ` Richard Purdie
2014-12-19 12:11       ` Enrico Scholz
2014-12-19 12:24         ` Richard Purdie
2014-12-23  2:07           ` Enrico Scholz
2014-12-23  8:54             ` Richard Purdie
2014-12-23 10:51               ` Enrico Scholz
2014-12-23 15:36                 ` Bruce Ashfield
2014-12-23 15:28               ` Bruce Ashfield
2014-12-10 10:34 ` [PATCH 3/7] kerneldev: create kernel-devsrc packaging Bruce Ashfield
2014-12-10 10:34 ` [PATCH 4/7] images: introduce core-image-kernel-dev Bruce Ashfield
2014-12-10 10:34 ` [PATCH 5/7] lttng/perf: depend on virtual/kernel:do_install Bruce Ashfield
2014-12-10 10:34 ` [PATCH 6/7] kernel-yocto: fix non-git builds Bruce Ashfield
2014-12-10 10:34 ` [PATCH 7/7] kernel-yocto: make sure git tags get dereferenced properly in do_patch() Bruce Ashfield

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=lyegrv99wr.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox