From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulf Samuelsson Date: Fri, 19 Oct 2007 10:35:11 +0200 Subject: [Buildroot] svn At revision 20289 breakage References: <4717A47F.4000908@asist.si> <4717C93A.3080401@promwad.com><0c3501c811c4$63522850$01c4af0a@Glamdring><4717D0BA.1050300@promwad.com><0c5901c811c6$8aecca30$01c4af0a@Glamdring> <4718510D.5030602@asist.si> <008201c81224$6c96bd80$01c4af0a@Glamdring> <4718671F.3040005@asist.si> <4718850D.9020302@promwad.com> Message-ID: <00da01c8122b$716ad6a0$01c4af0a@Glamdring> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net link: www.avrfreaks.net ----- Original Message ----- From: "Kuten Ivan" To: "Babarovic Ivica" Cc: "Ulf Samuelsson" ; Sent: Friday, October 19, 2007 12:21 PM Subject: Re: [Buildroot] svn At revision 20289 breakage > Babarovic Ivica wrote: >> Ulf Samuelsson wrote: >>> It is always the case that you have to provide a ".config" file for >>> linux. >>> >>> For some lucky souls Buildroot will do it for you. >>> This is when there is an appropriate definition somewhere in the >>> target directory, >>> and if you have supplied the right kernel. >> Well, I guess I was lucky until now. I never provided any kernel or >> .config files. >> I still fail to see why this is important for buildroot build. Kernel >> headers? >> >> I have a .config file from a kernel I build. Should I put that into >> buildroot process? >> What differences would it make? >>> For some unlucky souls, they now have an option to start a "make >>> xconfig" >>> to get a window allowing them to configure things instead of having a >>> failed build. >>> >> _______________________________________________ >> buildroot mailing list >> buildroot at uclibc.org >> http://busybox.net/mailman/listinfo/buildroot > > As for me, I'm not using building kernel in buildroot - I'm building it > separately. > And with recent changes made by Ulf, we have only to regenerate our > .config buildroot config > and to select Kernel -> "none". And I have buildroot build OK again. > The only thing that Ulf forget to warn people that if they have old > buildroot .config > they must regenerate it and select kernel .config or kernel none , > otherwise you will get that error > messages when doing cp. > 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. > Best regards, > Ivan Best Regards Ulf Samuelsson ulf at atmel.com Atmel Nordic AB Mail: Box 2033, 174 02 Sundbyberg, Sweden Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29 GSM +46 (706) 22 44 57