From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] First rootfile system build using buildroot
Date: Wed, 2 Sep 2015 14:59:01 +0100 [thread overview]
Message-ID: <55E700A5.3080403@imgtec.com> (raw)
In-Reply-To: <CAKpDV8vpO_2UUWUBssE6hDCV=Jh3b1sAeY4=V-b6xEazzdJAPg@mail.gmail.com>
Dear Katoch,
one quick question. Which one is your name, "Katoch" or "Dinesh Guleira"?
On 09/02/2015 02:54 PM, Dinesh Guleria wrote:
>>> You need to set
> BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
> in-tree defconfig file.
> Is this file an existing file or will be created at runtime ? If
> existing then where does this in-tree deconfig file lies in the
> buildroot directory ?
it is an existing defconfig file in the kernel tree, not in the
Buildroot tree. You can find them in "arch/<your architecture>/configs/".
If you want to use a custom defconfig file, then place it into the
Buildroot tree, maybe at $(TOPDIR), and use the appropriate option in
the Buildroot menuconfig.
Regards,
Vincent.
> Regards,
> Katoch
>
> Hi Katoch,
>
> On Wed, Sep 02, 2015 at 04:36:51PM +0530, Dinesh Guleria wrote:
>> I have successfully compiled a linux rootfs.Now I am trying to compile a
>> linux kernel using buildroot.
>> My kernel settings are ;--
>> Kernel version : 4.0.4
>> kernel configuration : use an in-tree deconfig file
>>
>> But i am getting following error, when make :--
>> linux/linux.mk:367 <http://linux.mk:367>: *** No kernel defconfig name
> specified, check your
>> BR2_LINUX_KERNEL_DEFCONFIG setting. Stop.
>
> This means that BR2_LINUX_KERNEL_DEFCONFIG is empty. You need to set
> BR2_LINUX_KERNEL_DEFCONFIG (label: "Defconfig name") to the name of your
> in-tree defconfig file.
>
> baruch
>
> --
> http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
> - baruch at tkos.co.il <mailto:baruch@tkos.co.il> - tel:
> +972.2.679.5364, http://www.tkos.co.il -
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2015-09-02 13:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 14:37 [Buildroot] First rootfile system build using buildroot Dinesh Guleria
2015-08-31 15:18 ` Dinesh Guleria
2015-08-31 15:53 ` Lee, Tommy
2015-08-31 17:17 ` Dinesh Guleria
2015-08-31 20:58 ` Lee, Tommy
2015-09-01 1:09 ` Dinesh Guleria
2015-09-01 6:58 ` Thomas Petazzoni
2015-09-01 11:25 ` Dinesh Guleria
2015-09-01 12:02 ` Dinesh Guleria
2015-09-01 12:14 ` Vicente Olivert Riera
2015-09-01 13:23 ` Dinesh Guleria
2015-09-01 15:54 ` Lee, Tommy
2015-09-01 15:57 ` Lee, Tommy
[not found] ` <CAKpDV8uny8GAJrEkEBmMdcboOrGuVQ4G09KRtL9yuvgH1XKE=Q@mail.gmail.com>
2015-09-01 17:45 ` Lee, Tommy
2015-09-02 0:29 ` Dinesh Guleria
2015-09-02 3:38 ` Baruch Siach
2015-09-02 11:06 ` Dinesh Guleria
2015-09-02 11:47 ` Baruch Siach
2015-09-02 13:54 ` Dinesh Guleria
2015-09-02 13:59 ` Vicente Olivert Riera [this message]
2015-09-02 14:51 ` Dinesh Guleria
2015-09-02 14:55 ` Vicente Olivert Riera
2015-09-02 16:57 ` Dinesh Guleria
2015-09-02 17:16 ` Baruch Siach
2015-09-02 17:58 ` Dinesh Guleria
2015-09-02 18:13 ` Dinesh Guleria
2015-09-02 18:24 ` Samuel Martin
2015-09-01 6:56 ` Thomas Petazzoni
2015-08-31 20:45 ` Thomas Petazzoni
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=55E700A5.3080403@imgtec.com \
--to=vincent.riera@imgtec.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