linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-embedded@vger.kernel.org
Subject: "make oldconfig" kills config options when cross compiling
Date: Thu, 15 May 2014 17:02:31 +0200	[thread overview]
Message-ID: <ll2ku7$uu$1@ger.gmane.org> (raw)

Hello,

I want to build an up-to-date kernel (3.14.4) based on this config:

<https://raw.githubusercontent.com/archlinuxarm/PKGBUILDs/master/core/linux-olinuxino/config>

To do so, I copied this config file as ".config" into the kernel source 
tree and executed

$ make ARCH=arm CROSS_COMPILE=/path/to/compiler/ oldconfig

My problem is, that this always drops important entries like 
"CONFIG_ARCH_MXS=y".

If I start with "make mxs_defconfig" and run "make oldconfig" on this 
default config, then no entries are killed.

What's wrong with the config, I want to start with?

Thanks in advance.

Greetings,

Manuel Reimer

             reply	other threads:[~2014-05-15 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 15:02 Manuel Reimer [this message]
2014-05-15 23:26 ` "make oldconfig" kills config options when cross compiling Randy Dunlap
2014-05-24 19:13   ` Manuel Reimer

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='ll2ku7$uu$1@ger.gmane.org' \
    --to=manuel.spam@nurfuerspam.de \
    --cc=linux-embedded@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).