IS that the right compiler ? I do not think so . . . should be the hf compiler for the BBB. Maybe I'm wrong ?
On Mon, Jul 21, 2014 at 1:08 PM, Mark A. Yoder <mark.a.yo...@gmail.com> wrote: > Are you scripts smart enough to install the right cross compilers? Do I > need *sudo apt-get install gcc-arm-linux-gnueabi?* > > --Mark > > > On Monday, July 21, 2014 4:05:15 PM UTC-4, Mark A. Yoder wrote: >> >> Let me summarize.... Here is what I tell my students: >> >> host$ *sudo apt-get install gcc-arm-linux-gnueabi* >> host$ *git clone >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git >> <http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git> >> ~/linux-src* >> host$* git clone https://github.com/RobertCNelson/bb-kernel.git >> <https://github.com/RobertCNelson/bb-kernel.git>* >> host$ cd bb-kernel >> host$ *git tab *(This shows what versions are available) >> host$ *git checkout 3.8.13-bone60 -b v**3.8.13-bone60* >> host$ *./build_kernel.sh* >> >> If we don't edit system.sh is it able to figure out what cross compilers >> to use and how to set ZRELADDR? >> >> host$ *./dpkg_check.sh * >> trusty >> ii libncurses5-dev:amd64 >> 5.9+20140118-1ubuntu1 amd64 >> developer's libraries for ncurses >> >> --Mark >> >> >> On Monday, July 21, 2014 3:45:28 PM UTC-4, RobertCNelson wrote: >>> >>> On Mon, Jul 21, 2014 at 2:17 PM, Robert Nelson <robert...@gmail.com> >>> wrote: >>> > On Mon, Jul 21, 2014 at 2:11 PM, Mark A. Yoder <mark.a...@gmail.com> >>> wrote: >>> >> I'm pulling together some notes for my students[1] on installing and >>> >> compiling different kernels for BeagleBone Black. >>> >> >>> >> The installing side is now easy with the latest (2014-7-16) Debian >>> image. >>> >> Run: >>> >> >>> >> apt-cache pkgnames | grep linux-image >>> >> >>> >> to see what images are out there and then: >>> >> >>> >> apt-get install linux-image-3.8.13-bone60 >>> >> >>> >> to install the image of your choice. But what if you want to compile >>> your >>> >> own? >>> >> >>> >> Are these the best way to do it from scratch? >>> >> >>> >> host$ git clone git://github.com/RobertCNelson/linux-dev.git >>> >> host$ cd linux-dev >>> > >>> > Use "bb-kernel" instead of "linux-dev" (less 'other' noise for users >>> > going on in that repo) >>> > >>> >> host$ git checkout origin/am33x-v3.8 -b am33x-v3.8 >>> >> host$ cp system.sh.sample system.sh >>> >> host$ ./build_kernel.sh >>> >> >>> >> How do I see what versions are available for checkout? How do I >>> compile a >>> >> specific version, such as 3.8.13-bone60? >>> > >>> > There is also: >>> > https://github.com/RobertCNelson/linux-stable-rcn-ee/branches/all >>> > >>> > Just prototyping it right now, planning to move it to: >>> > >>> > https://github.com/beagleboard/linux >>> > >>> > >>> >> >>> >> Once I've gotten something to compile and work should I: >>> >> >>> >> host$ git checkout -b myBranch >>> >> >>> >> so I can easily track the changes I make? Do I just run >>> ./build_kernel.sh >>> >> again to recompile? >>> > >>> > So "./build_kernel.sh" will always "nuke" ./KERNEL/ but it'll build it >>> > based on patches/defconfig & patch.sh >>> > >>> > "./tools/rebuild.sh" will allow you to 'rebuild" ./KERNEL/ as is, say >>> > your working on a kernel patch but haven't commited it to the >>> > patch.sh/patches_dir... >>> > >>> > >>> >> Thanks, your answers will help me guide my students... >>> >> >>> >> --Mark >>> >> >>> >> [1] >>> >> http://elinux.org/EBC_Exercise_08_Installing_ >>> Development_Tools#Getting_the_3.8_Kernel >>> >>> BTW, here's a couple things to help out: >>> >>> If you do: >>> >>> git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- >>> stable.git >>> ~/linux-src >>> >>> The scripts will automatically find that location, so you can ignore >>> changing system.sh >>> >>> and do me a favor on precise, run: >>> >>> ./repo_maintenance/dpkg_check.sh >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> http://www.rcn-ee.com/ >>> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
