From: Kuten Ivan <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn At revision 20289 breakage
Date: Fri, 19 Oct 2007 09:45:27 -0100 [thread overview]
Message-ID: <47188AC7.1000503@promwad.com> (raw)
In-Reply-To: <00da01c8122b$716ad6a0$01c4af0a@Glamdring>
>
> It was Bernhard which introduced the new kernel selection so dont blame me.
>
> The old way of building the kernel really suck, so I understand why you
> build it separately.
>
> I added the Advanced Kernel Configuration last week to fix those problems.
> You can select any 2.6.x.y kernel.
> You can add -rc# patches, -mm# patches and your own proprietary patch which
> is located in $(DL_DIR)
> You can select easily zImage,bzImage, uImage, vmlinux (proprietary).
> It would be good if you gave that one a try and provide feedback on any
> drawbacks you see.
>
Sorry Ulf, I did not want to blame anybody.
Yeah, for me it was quite surprising that having buildroot .config which was working
for several months to see that it's not working anymore.
OK, i'll try building kernel within buildroot and will inform about results.
Best regards,
Ivan
--
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
prev parent reply other threads:[~2007-10-19 10:45 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
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 [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=47188AC7.1000503@promwad.com \
--to=ivan.kuten@promwad.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