From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_PACKAGE_BUSYBOX_CONFIG not working fine
Date: Fri, 11 Dec 2015 23:27:07 +0100 [thread overview]
Message-ID: <566B4DBB.6010105@mind.be> (raw)
In-Reply-To: <CAKpDV8u01myqCx7ROq9C_7B9Wgomb8Assh_SmUeyCRAc3UkAXQ@mail.gmail.com>
On 11-12-15 12:07, Dinesh Guleria wrote:
> Hi,
>
> I am following steps 4 & 5 in this link
> :--https://buildroot.org/downloads/manual/manual.html#_quick_guide_to_storing_your_project_specific_customizations
>
> I am running following command :--- make busybox-update-config
> BR2_PACKAGE_BUSYBOX_CONFIG=/home/dinesh/busybox/busybox.config
Please check yout spelling. The screenshot you posted has
BR2_PACKAGE_BUSYBOX_CONFIG_FILE=... .
You may notice that computers are not so forgiving when it comes to spelling
mistakes.
Regards,
Arnout
>
> But busybox .config file doesn't go to right path set
> "/home/dinesh/busybox/busybox.config".
>
> Please suggets why is it going to location "package/busybox/busybox.config" ?
>
> See the attached image.
>
> Regards,
>
> Dinesh
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-12-11 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 11:07 [Buildroot] BR2_PACKAGE_BUSYBOX_CONFIG not working fine Dinesh Guleria
2015-12-11 22:27 ` Arnout Vandecappelle [this message]
2015-12-12 6:45 ` Dinesh Guleria
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=566B4DBB.6010105@mind.be \
--to=arnout@mind.be \
--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 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.