Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rscr <rafacrespiramon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Custom tarball and .config file
Date: Fri, 13 Dec 2019 06:27:33 -0600 (CST)	[thread overview]
Message-ID: <1576240053124-0.post@n4.nabble.com> (raw)
In-Reply-To: <1576133977989-0.post@n4.nabble.com>

Hello, 

I don't know what I am doing wrong, but I am still not able to configure the
kernel through "linux-menuconfig". I* would like to use the bcmrpi_defconfig
as base and add my kernel driver as <M>. How can I achieve it? *

My steps:

a) I've got my kernel source (linux-rpi-4.19.y) in /home/tec/rcr/tools/src
with the driver.c, Makefile and Kconfig edited (I can build the kernel
source outside of buildroot)
b) Tar the kernel source
c) I go into buildroot's directory. I've myproject_defconfig file into
br2_external so I run:
make BR2_EXTERNAL=~/rcr/projects/cp4/rscr_br2_extree myproject_defconfig
make menuconfig

myproject_defconfig.myproject_defconfig
<http://buildroot-busybox.2317881.n4.nabble.com/file/t2824/myproject_defconfig.myproject_defconfig>  

e) Once the buildroot config is done, I run:
make linux-menuconfig

I get the following error:

make[2]: *** No rule to make target 'bcmrpi_defconfig'.  Stop.
linux/linux.mk:565: recipe for target
'/home/ibercomp/rcr/projects/cp4/buildroot/output/build/linux-custom/.stamp_dotconfig'
failed


What I am doing wrong?

Kind Regards




--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

      reply	other threads:[~2019-12-13 12:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  7:54 [Buildroot] Custom tarball and .config file rscr
2019-12-10 13:11 ` Thomas Petazzoni
2019-12-10 13:58   ` rscr
2019-12-12  6:59     ` rscr
2019-12-13 12:27       ` rscr [this message]

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=1576240053124-0.post@n4.nabble.com \
    --to=rafacrespiramon@gmail.com \
    --cc=buildroot@busybox.net \
    /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