• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 4091 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

error while Building Yocto Filesystem

Michael john
Intellectual 395 points

Hi

 I use omap5432

follow the guide ,I build yocto filesystem ,but when I run   "./build-core-sdk.sh omap5-evm",there is error;


the below is the process,in the last

robot@ubuntu:~/ti-glsdk_omap5-uevm_6_03_00_01$ cd yocto-layers
robot@ubuntu:~/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers$ ./build-core-sdk.sh omap5-evm
[GLSDK]>
[GLSDK]> Current Directory is /home/robot/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers
[GLSDK]> PATH is /home/robot/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/arm-linux-gnueabihf/bin:/home/robot/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
[GLSDK]> Building on ubuntu running Linux ubuntu 3.11.0-15-generic #25~precise1-Ubuntu SMP Thu Jan 30 17:39:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[GLSDK]> Starting Yocto build at Sun May 11 22:06:41 CST 2014
[GLSDK]>
[GLSDK]> ./oe-layertool-setup.sh -f configs/glsdk/glsdk-06.03.00.01-config.txt
/home/robot/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers


cloning repo bitbake

Fetching origin
/usr/local/bin/git-proxy: line 17: /usr/bin/nc: No such file or directory
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
Previous HEAD position was bbb4fa4... methodpool: Retire it, remove global method scope
Switched to branch 'master'
Already up-to-date.
Note: checking out 'bbb4fa427739912ff3b87379bf629066f6662458'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at bbb4fa4... methodpool: Retire it, remove global method scope


cloning repo meta-arago

Fetching origin
/usr/local/bin/git-proxy: line 17: /usr/bin/nc: No such file or directory
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
Previous HEAD position was b838c23... ti-compat-wireless-wl18xx: build from ol_r8.a8.08
Switched to branch 'master'
Already up-to-date.
Note: checking out 'b838c23aae724496b3aee48b5daa0f458e0526c1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at b838c23... ti-compat-wireless-wl18xx: build from ol_r8.a8.08


cloning repo meta-qt5

Fetching origin
/usr/local/bin/git-proxy: line 17: /usr/bin/nc: No such file or directory
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
Previous HEAD position was 775d77e... qtwebkit: Depend on gstreamer-1.0 instead of 0.10
Switched to branch 'master'
Already up-to-date.
Note: checking out '775d77e482f1ea203c78003cccd2547075fd720f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 775d77e... qtwebkit: Depend on gstreamer-1.0 instead of 0.10


cloning repo meta-openembedded

Fetching origin
/usr/local/bin/git-proxy: line 17: /usr/bin/nc: No such file or directory
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
Previous HEAD position was 4475420... net-snmp: Backport fix for NETSNMP_NO_SYSTEMD typos
Switched to branch 'dylan'
Already up-to-date.
Note: checking out '44754206632dd5b0725aeb43e99e4ff9e0245dca'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 4475420... net-snmp: Backport fix for NETSNMP_NO_SYSTEMD typos


cloning repo meta-ti

Fetching origin
/usr/local/bin/git-proxy: line 17: /usr/bin/nc: No such file or directory
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
Previous HEAD position was 691ad44... libdri2: Define license
Switched to branch 'dylan'
Already up-to-date.
Note: checking out '691ad445d8d55971ac787a60516aaf91bc4bc3a3'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 691ad44... libdri2: Define license


cloning repo meta-linaro

Fetching origin
/usr/local/bin/git-proxy: line 17: /usr/bin/nc: No such file or directory
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
Switched to branch 'dylan'
Already up-to-date.
Note: checking out 'c9f78d6eff14ada3f2bc960e81883b27a10afecc'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at c9f78d6... busybox: enable CONFIG_FEATURE_TAR_NOPRESERVE_TIME


cloning repo oe-core

Fetching origin
/usr/local/bin/git-proxy: line 17: /usr/bin/nc: No such file or directory
fatal: The remote end hung up unexpectedly
error: Could not fetch origin
Previous HEAD position was 394fa61... libsoup-2.4: add intltool-native to DEPENDS
Switched to branch 'dylan'
Already up-to-date.
Note: checking out '394fa61d00b97c19610bfb38f02174c4e8aeeb15'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 394fa61... libsoup-2.4: add intltool-native to DEPENDS


################################################################################
The bblayers.conf configuration file has been created for you with some
default values.  Please verify the contents of your conf/bblayers.conf
file for correctness.

NOTE: Any additional entries to this file will be lost if the ./oe-layertool-setup.sh
      script is run again.  To add entries permanently to this file
      please add them to the config file used and rerun the
      ./oe-layertool-setup.sh script.



################################################################################
The local.conf configuration file has been created for you with some
default values.  Please verify the contents of your conf/local.conf
file for correctness.

By default the number of threads used by the build is set to the number
of CPUs found on your system.

NOTE: You will probably want to change the default MACHINE setting in the
      local.conf file to the machine you are trying to build.

WARNING: Found existing /home/robot/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers/build/conf/local.conf
Saving a backup to /home/robot/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers/build/conf/local.conf.bak
./oe-layertool-setup.sh: 745: [: x: unexpected operator


################################################################################
A setenv file has been created for you in the conf directory.  Please verify
The contents of this file.  Once you have verified the contents please source
this file to configure your environment for building:

    . conf/setenv

You can then start building using the bitbake command.  You will likely want
to set the MACHINE option if you have not done so in your local.conf file.

For example:
    MACHINE=xxxxx bitbake <target>

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-toolchain-sdk
    adt-installer
    meta-ide-support
[GLSDK]> cd build
[GLSDK]> . conf/setenv
[GLSDK]> cp conf/local.conf conf/local.conf.pristine
[GLSDK]> echo ARAGO_BRAND = "glsdk" >> conf/local.conf
In which directory do you want to place the downloads for the Yocto build ?(if this directory does not exist it will be created)
Ensure that complete path is provided.
[ /home/robot/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers/downloads ]
[GLSDK]> MACHINE=omap5-evm bitbake arago-glsdk-multimedia-image
Pseudo is not present but is required, building this first before the main build
ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/robot/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/bin/arm-linux-gnueabihf-gcc -v' failed: command not found
ERROR: Failed to obtain external Linaro toolchain version: Execution of '/home/robot/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/bin/arm-linux-gnueabihf-gcc -v' failed: command not found
Loading cache: 100% |###########################################| ETA:  00:00:00
Loaded 121 entries from dependency cache.
ERROR: ExpansionError during parsing /home/robot/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers/sources/meta-arago/meta-arago-extras/recipes-core/meta/external-arago-sdk-toolchain.bb: Failure expanding variable ARG_VER_GCC[:=], expression was ${@arg_get_gcc_version(d)} which triggered exception OSError: [Errno 2] No such file or directory
ERROR: Command execution failed: Exited with 1

Summary: There were 4 ERROR messages shown, returning a non-zero exit code.
[GLSDK]>
[GLSDK]> Completed Yocto build at Sun May 11 22:06:50 CST 2014
[GLSDK]>
robot@ubuntu:~/ti-glsdk_omap5-uevm_6_03_00_01/yocto-layers$

best regards

 Michael

  • 0
    TI__Guru**** 161600 points

    Hello Michael,

    The highlighted (in red) errors indicate that the make system cannot find the path to your gcc cross compiler: /home/robot/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/bin/
    The cross compiler is installed when running the setup.sh script in the GLSDK.

    1. The first thing to do is check if the linaro cross compiler (gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux) is properly installed, all of its components, such as arm-linux-gnueabihf-ar, arm-linux-gnueabihf-c++, arm-linux-gnueabihf-gcc, arm-linux-gnueabihf-gcc-4.7.3 and so on, are available.

    If not then install it in the appropriate directory (as I see from the log it should be:  /home/robot/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/)

    2. If everything from 1) is available, try exporting the build variables before executing the build-core-sdk.sh script. That is:
     # export ARCH=arm

     # export PATH=<path to gcc cross copmiler>/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/bin:$PATH

    # export CROSS_COMPILE= <path to gcc cross copmiler>/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux/bin/arm-linux-gnueabihf-

    and then execute the ./build-core-sdk.sh omap5-evm command.

    Best Regards,

    Yordan

     

  • 0 in reply to Yordan Kovachev
    Intellectual 395 points

    Hi Yordan

    you are right ,The cross compiler isn't  installed properly,

    but I remember there is no error and interrupt when running the setup.sh script in the GLSDK.it should be installed .

    how to installed the gcc cross compiler again .what command or what script I can execute.

    you tell me I should install all of its components,

    such as arm-linux-gnueabihf-ar,

    arm-linux-gnueabihf-c++,

    arm-linux-gnueabihf-gcc,

    arm-linux-gnueabihf-gcc-4.7.3 and so on

    are these the all components?
    I cann't find arm-linux-gnueabihf-c++.

    best regards

    Michael

     

  • 0 in reply to Michael john
    TI__Guru**** 161600 points

    Michael,

    First of all the listed arm-linux-gnueabihf-xxxxx components are only part of the components in gcc cross compiler, there are many more.

    The cross compiler is installed automatically by the setup.sh script.

    The setup.sh script is an interactive script, it asks the user to point a directory to which the GCC cross compiler should be installed (if no path is specified it installs it to a pointed default directory).  You should have seen a couple of message asking you:
    1) To use the SDK, you need to have Linaro cross compiler toolchain installed

         Do you want to install it now Y/n

    2) In which directory do you want to fetch the cross compiler on the host?(if this directory does not exist it will be created)

    If you don't specify a directory, the script installs it in ~/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux folder.


    If you have answered with "n" to 1), you can manually download and extract the cross compiler to a desired folder. The link from which the scripts extract cross compiler is: https://launchpad.net/linaro-toolchain-binaries/trunk/2013.03/+download/gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux.tar.bz2

    Best Regards,
    Yordan