All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: Kernel config fragments ignored
Date: Mon, 29 May 2017 09:38:21 -0500	[thread overview]
Message-ID: <1496068701.26945.32.camel@linux.intel.com> (raw)
In-Reply-To: <8C8F5C9C1BB04040A6555EFD5B0B5131@PAULD>

On Mon, 2017-05-29 at 00:21 -0700, Paul D. DeRocco wrote:
> I ported a working build from Fido to Morty, made a few tweaks in response
> to error messages (mostly updating version numbers), but it's not finding
> my kernel configuration fragments. This is supposed to be an i386 arch
> system, but it insists upon building an x86_64 kernel. The .config file it
> generates does not include my configuration fragments, which contain
> things like CONFIG_X86_64=n and CONFIG_X86_32=y.
> 

I hit a similar error when using the yocto-bsp script to create a i386
machine then building the kernel. Can you try what is suggested on poky
commit

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=19e99786beeaf792094a4ed9859de00c064674b2



> My linux-yocto-rt_4.8.bbappend file lists my .cfg and .scc files in
> SRC_URI, and they are indeed being copied into the build directory (at
> tmp/work/chroma_bsp-poky-linux/linux-yocto-rt/4.8.12+blahblah). The docs
> seem to imply that that's all I have to do: that they will automatically
> be found and included, without my having to name them anywhere else. If I
> intentionally put a syntax error into any of them, that erroneous file is
> indeed copied, but nothing ever complains about the error, so it isn't
> being read when I force a kernel_configme. Even cleaning the kernel and
> repeating the kernel_configme doesn't change anything.
> 
> There is one .scc that includes the others, so that suggests that there
> must be some mechanism for specifying that one and relying on the explicit
> includes to pull in the rest. Its name is chroma-bsp.scc, which matches my
> custom machine name specified in local.conf. It was previously called
> chroma-bsp-preempt-rt.scc under Fido, but when that didn't work under
> Morty, I tried changing the name, to no avail.
> 
> Also, I'm puzzled that the work directory name contains "chroma_bsp"
> instead of "chroma-bsp".
> 
> What am I missing?
> 
> -- 
> 
> Ciao,               Paul D. DeRocco
> Paul                mailto:pderocco@ix.netcom.com
> 




  reply	other threads:[~2017-05-29 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29  7:21 Kernel config fragments ignored Paul D. DeRocco
2017-05-29 14:38 ` Leonardo Sandoval [this message]
2017-05-31  1:15 ` Paul D. DeRocco
2017-05-31  1:25   ` 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=1496068701.26945.32.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=pderocco@ix.netcom.com \
    --cc=yocto@yoctoproject.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.