"Starting Compiling" the hard way

Discussion in 'General Discussion' started by tacolover, Jul 21, 2014.

  1. tacolover

    tacolover New Member

    Joined:
    Jan 30, 2014
    Messages:
    3
    Likes Received:
    0
    Let me first start off by saying I am very new to software and code for computers. I am trying to create a bootable micro sd card the hard way from the udoo manual. Everything has run smoothly until the part where the manual says to "make -j4 CROSS_COMPILE=../arm-fsl-linux-gnueabi/bin/arm-fsl-linux-gnueabi- ARCH=arm uImage modules". I typed it in the terminal after complete all prior steps and the terminal ask a couple hundred questions such as what type of compression and what processor family the udoo is in. Is this normal? After completely all the questions the terminal reads "error". Am I doing something wrong? Any advice would help.



    Thanks,



    Luke
     
  2. peter247

    peter247 New Member

    Joined:
    Mar 10, 2014
    Messages:
    263
    Likes Received:
    2
    The way I compile is native , eg compile on the udoo it`s self which is a lot slower , but you don`t need any toolchain etc.

    So :

    make -j4 CROSS_COMPILE=../arm-fsl-linux-gnueabi/bin/arm-fsl-linux-gnueabi- ARCH=arm uImage modules"

    native is now just :- make -j4 uImage modules"

    my step to compiling are :

    apt-get install build-essential libncurses5-dev
    apt-get install git
    apt-get install uboot-mkimage

    git clone https://github.com/UDOOboard/Kernel_Unico kernel
    cd kernel
    make UDOO_defconfig
    make menuconfig <---- change bits
    make -j4 uImage && make -j4 modules && make modules_install
     

Share This Page