Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Burghart <mb@michaelburghart.de>
To: buildroot@busybox.net
Subject: [Buildroot] Making kernel?
Date: Fri, 08 Apr 2011 09:26:15 +0200	[thread overview]
Message-ID: <4D9EB897.4050507@michaelburghart.de> (raw)
In-Reply-To: <4D9EA40C.2020208@michaelburghart.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi again,

where the hell is it looking for its defconfig files???? I manually
copied it across the whole filesystem but the script doesn't find it.
What can I do??


Am 08.04.2011 07:58, schrieb Michael Burghart:
> Good morning Daniele, good morning list,
> 
> I wanted to generate my own kernel but I get a bit confused.
> What does
> 
> linux/linux.mk:197: *** No kernel configuration file specified, check
> your BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE setting.
> 
> mean? There is an .config file. I even refuses a "make linux-menuconfig"
> It doesn't give me the chance of building my own kernel. What do I do wrong?
> 
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

- -- 
- --
cheers
- -micha-
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNnriXAAoJEEMkp/gkis19zHgH/2xjGV91C7kpc4BPYWM5xyA3
m1RZjznWXM9B3EBZgW2MP9enkBFFqlLZpY8Mwvx9kq4Sy1tuK+3PgfK1/8/Fqe3g
EaCbvu/OIdwzvj9a6Kup44FlknI1ikDY8SktN7tX9T8DmLmNaW55WoLlJc2OIitm
MVFJaEMXlrn2SWbXTbAhz2BhY9G3sseQ3h7LCM1o9Hamcj/PddCE299ik3MMkx0w
MW7a758DC3lnjmU9guY/0M5DcQPVizAocjJypjzmlRRZPUHHmIvj1IWabRfZTNIk
wifIqc56e4RuHzcdR2KIOMuZAJrPK9dWQxq959ZwsmV4eYbzMThk4rBAHCvjm14=
=S0Dy
-----END PGP SIGNATURE-----

  reply	other threads:[~2011-04-08  7:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 11:20 [Buildroot] Binary ATI driver package in buildroot Allan W. Nielsen
2011-04-06 11:20 ` [Buildroot] [PATCH] fglrx: Added package for ATI's binary device driver Allan W. Nielsen
2011-04-06 13:35 ` [Buildroot] Binary ATI driver package in buildroot Thomas Petazzoni
     [not found]   ` <BANLkTinVhQdOqVJdkO9gK8Q==1j1uf_=BA@mail.gmail.com>
2011-04-06 14:42     ` Thomas Petazzoni
2011-04-07 12:51       ` Allan Nielsen
2011-04-07  6:37   ` [Buildroot] Apache CrossCompile recipe Michael Burghart
2011-04-07  6:59     ` [Buildroot] [OT] " Patryk Benderz
     [not found]     ` <4D9D6EDE.7050004@daccii.it>
     [not found]       ` <4D9D6F6B.6000801@michaelburghart.de>
     [not found]         ` <4D9D7131.3090705@itechcon.it>
2011-04-07  8:20           ` [Buildroot] " Michael Burghart
     [not found]             ` <4D9D75DB.2010005@itechcon.it>
     [not found]               ` <4D9D775A.5010506@michaelburghart.de>
     [not found]                 ` <4D9D7EE5.6060200@itechcon.it>
     [not found]                   ` <4D9DE9B2.1000100@michaelburghart.de>
     [not found]                     ` <4D9DFE83.3080602@itechcon.it>
2011-04-07 18:22                       ` Michael Burghart
2011-04-08  5:58                       ` [Buildroot] Making kernel? Michael Burghart
2011-04-08  7:26                         ` Michael Burghart [this message]
2011-04-08  7:32                           ` Michael Burghart
2011-04-08  7:50                             ` bruce bushby
2011-04-08  9:20                               ` Michael Burghart
     [not found]                       ` <4D9E5FAD.8020408@michaelburghart.de>
     [not found]                         ` <4D9EFFBE.70308@itechcon.it>
2011-04-08 12:50                           ` [Buildroot] Apache CrossCompile recipe Michael Burghart
2011-04-08 13:15                             ` Daniele Salvatore Albano
2011-04-13 14:53                               ` Michael Burghart
2011-04-09  6:12                           ` Michael Burghart
2011-04-09 23:20                             ` bruce bushby
2011-04-09 23:49                               ` Michael Burghart

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=4D9EB897.4050507@michaelburghart.de \
    --to=mb@michaelburghart.de \
    --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