All of lore.kernel.org
 help / color / mirror / Atom feed
From: Babarovic Ivica <ivica.babarovic@asist.si>
To: buildroot@busybox.net
Subject: [Buildroot] svn At revision 20289 breakage
Date: Fri, 19 Oct 2007 08:39:09 +0200	[thread overview]
Message-ID: <4718510D.5030602@asist.si> (raw)
In-Reply-To: <0c5901c811c6$8aecca30$01c4af0a@Glamdring>

Ulf Samuelsson wrote:
>>>
>>> Key question:
>>>
>>> What does
>>>
>>> $ cp a
>>>
>>> do?
>>>
>>> Best Regards
>>> Ulf Samuelsson
>>>
>>
>> target/linux/Makefile.in : line 148
>>
>> $(LINUX26_DIR)/.configured: $(LINUX26_DIR)/.patched $(LINUX26_KCONFIG)
>>        cp -dpf $(LINUX26_KCONFIG) $(LINUX26_DIR)/.config
>>        $(SED) '/CONFIG_AEABI=y/d' $(LINUX26_DIR)/.config
>>
>>
>> and LINUX26_KCONFIG is "" because BR2_PACKAGE_LINUX_KCONFIG=""
>>
>>
>
> Gotcha!
>
> Why not try the "Advanced Linux configuration" recently added
> This should allow you to do "make xconfig" to create the needed file.
>
Wait! so we should now include our kernel .config files in buildroot 
build process?
If so Why?

BR,
I.

  parent reply	other threads:[~2007-10-19  6:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 18:22 [Buildroot] svn At revision 20289 breakage Babarovic Ivica
2007-10-18 20:59 ` Ivan Kuten
2007-10-18 20:20   ` Ulf Samuelsson
2007-10-18 21:31     ` Ivan Kuten
2007-10-18 20:33       ` Ulf Samuelsson
2007-10-18 20:36       ` Ulf Samuelsson
2007-10-18 21:58         ` Ivan Kuten
2007-10-19  6:39         ` Babarovic Ivica [this message]
2007-10-19  7:32           ` Babarovic Ivica
2007-10-19  7:45           ` Ulf Samuelsson
2007-10-19  8:13             ` Babarovic Ivica
2007-10-19  8:20               ` Ulf Samuelsson
2007-10-19 10:21               ` Kuten Ivan
2007-10-19  8:35                 ` Ulf Samuelsson
2007-10-19 10:45                   ` Kuten Ivan

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=4718510D.5030602@asist.si \
    --to=ivica.babarovic@asist.si \
    --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.