Yes, you touch the pain area I am facing. I could build x86 as well as i386 toolchain. Though I have not tried the image yet.
But when cross compiling arm and arm64 say for example, I receive .config related errors which either does not create the .config or gives errors like I mentioned. Would I be able to do a allyesconfig for this? If yes, what options needs to be missed or edited to get the processor selection at
runtime.
>> using i386 machine
$make ARCH=arm defconfig -> ends up with errors of hardware conpatibility of i386, .config not created
$make ARCH=arm allyesconfig -> ends up with errors of hardware conpatibility specially sub-architecture of processor, .config not created
$make ARCH=arm menuconfig -> all options enabled gives while building, .config created but kernel not built while using make
TnR,
Ganesh
Ganesh
From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
To: Ganesh B <ganeshsurfs@xxxxxxxxx>
Cc: "kernelnewbies@xxxxxxxxxxxxxxxxx" <kernelnewbies@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, January 9, 2013 12:20 PM
Subject: Re: Cross Compiling a different architechture
On Wed, Jan 9, 2013 at 12:06 PM, Ganesh B <ganeshsurfs@xxxxxxxxx> wrote:
Okay makes sense let me try clean before building different arch. I am not doing this at the moment. Would I need to have different toolchains for same architecture, I was trying to build for all processor types for an arch using a different toolchain but it failed?
You _may_ require different toolchains for different processor with same arch types, for example under x86, i386 and i586 toolchains _may_ be used interchangably but not ia64 or x86_64 or may not even for atom. Similarly in ARM, there are different families of processor and there may be big endian or small endian processor. So you may have to find the correct toolchain for the given config.
Ones that passed the different cross-compile arch failed at some modules speciially the net, sound, video, or built_in sections. Let me check this and revert.Have you ever compiled a complete end to end allyesconfig for a same or cross-compile build? allyesconfig gave me dependency/ missing/ invalid entry errors for cross-compile arch like arm.
Why would you do enable all config options? There may be incompatible dependencies, which will ofcourse lead to compilation errors.
I generally get .config files from elsewhere, sometimes there are files inside the source somewhere or sometimes you just do make ARCH=XXX menuconfig and then configure the options selectively.
I may try to build toolchain for raspberry pi in few days and see if I face such issues or not(but that is highly tentative. )
I generally get .config files from elsewhere, sometimes there are files inside the source somewhere or sometimes you just do make ARCH=XXX menuconfig and then configure the options selectively.
I may try to build toolchain for raspberry pi in few days and see if I face such issues or not(but that is highly tentative. )
TnR,
GaneshCc: "kernelnewbies@xxxxxxxxxxxxxxxxx" <kernelnewbies@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, January 9, 2013 11:19 AM
Subject: Re: Cross Compiling a different architechture
On Wed, Jan 9, 2013 at 3:30 AM, Ganesh B <ganeshsurfs@xxxxxxxxx> wrote:I do not know why but whether ncurses or menuconfig the build fails at some modules (specially hardware architecture ones), specially at cross compiling architecture build stage. It went smoothly for same system architecture like i386 or x86 but not for arm or arm64.
Where is the doc's for Kernel defconfig and kconfig in Kernel.org? I am trying to make and edit each manually for each architecture and then run make all. The problem is it is not allowing me to assemble all sub-architectures for say arm or arm64 as a dynamic module. I have to specify and select each option (sub-hardware architecture) specifically during build of defconfig for the architecture. My x86 is also blocking the build at times. I did not get anything good on my google search.I would say a wiser choice would be getting a .config from somewhere and editing options which you really need to change.
I am not sure if you understand this or not, but you need to have a series of toolchains for each arch you need to cross compile at different locations.
For different binaries of different arch, I would suggest you use different directories of same source code. Generally make clean or distclean should get rid of most binaries, but starting a clean build is always the best idea.
Toolchains can be bit of a pain to get right.w.r.t. Knoppix, Thank you, let me check the informit link for the architecture and usage relevance.TnR,
Ganesh
From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
To: Ganesh B <ganeshsurfs@xxxxxxxxx>
Cc: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>; "kernelnewbies@xxxxxxxxxxxxxxxxx" <kernelnewbies@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, January 8, 2013 8:44 PM
Subject: Re: Cross Compiling a different architechture
On Tue, Jan 8, 2013 at 2:39 PM, Ganesh B <ganeshsurfs@xxxxxxxxx> wrote:
Creating Defconfig and menuconfig (options) for all in one system from kernel. I want a clean build rather than an external mount, most I found did not have documentation.there is extensive documentation under Documentation/ directory in kernel source.
on simple search I got this link about building kernel on knoppix:
http://www.informit.com/articles/article.aspx?p=422949&seqNum=3
pretty much on most distribution, you can install ncurses and go for make menuconfig and then just make(i.e. if you are native compiling the kernel).
However the config for distributions are fairly complex these days, so you may require to build few other things like initrd and create devices files and all. Please refer to distro documentation for knoppix: http://knoppix.net/wiki/Main_Page
I would recommend that you read these guidelines before asking any question on this list
http://kernelnewbies.org/mailinglistguidelines
TnR,
GaneshCc: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>; "kernelnewbies@xxxxxxxxxxxxxxxxx" <kernelnewbies@xxxxxxxxxxxxxxxxx>
Sent: Tuesday, January 8, 2013 9:18 AM
Subject: Re: Cross Compiling a different architechture
Hi> Any help with some doc's. I see a defconfig for all, but the tree is not
On Tue, Jan 8, 2013 at 10:36 AM, Ganesh B <ganeshsurfs@xxxxxxxxx> wrote:
> Hello,
>
> clear. Any documentation support for this in .Kconfig and .defconfig?
Which config option you're not clear? Asking like this will only put
you in the blue, you know....
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
Thank you
Warm Regards
Anuz
--
Thank you
Warm Regards
Anuz
--
Thank you
Warm Regards
Anuz
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
