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.

c6678 kernel build configuration fails

When I follow the instructions to configure the Linux-c6x-2.0-beta2 from the downloaded tar files, I am getting the following:

sard@sard-desktop:~/my-linux-c6x/linux-c6x-2.0-beta2/linux-c6x-project$ ./prj config
scripts/setup

distro == Ubuntu
all following packages already installed: build-essential git-core expect automake
/bin/sh looks like bash
Installing gcc release 4.5-124 from cs public site site
Installing gcc tool chain to /home/sard/my-linux-c6x/linux-c6x-2.0-beta2/gcc-c6x
Installing uclibc source under /home/sard/my-linux-c6x/linux-c6x-2.0-beta2/gcc-c6x-uclibc
Downloading gcc tool chain binary https://support.codesourcery.com/GNUToolchain//package9095/c6x-uclinux/c6x-4.5-124-c6x-uclinux-i686-pc-linux-gnu.tar.bz2
--2011-08-15 16:34:03--  https://support.codesourcery.com/GNUToolchain//package9095/c6x-uclinux/c6x-4.5-124-c6x-uclinux-i686-pc-linux-gnu.tar.bz2
Resolving support.codesourcery.com... failed: Name or service not known.
wget: unable to resolve host address `support.codesourcery.com'

What is happening here, and do you have an idea of the solution to this problem?

I have already installed the Codesourcery toolchain for the c6x; does it need to be installed again?

  • When running "./prj config", it will try to install CodeSourcery automatically. You don't need to install it yourself. I think the http_proxy isn't set up in your case. Could you try to set up http_proxy and https_proxy?

    export http_proxy=webproxy.ext.ti.com
    export https_proxy=webproxy.ext.ti.com

    Rex

  • Rex,

    You were correct.  These two environment variables were not set and that would solve the problem.

    However, I did not see any reason to download CCS and the Codesourcery tools again. I examined the file

    linux-c6x-2.0-beta2/linux-c6x-project/setenv

    and at the end of the script it had commented lines where I could specify the explicit path locations of the already existing tools. I entered the locations and uncommented the lines. The original setenv file was missing a commented line for the variable XDAIS_DIR that should be inserted for completeness of documentation:

    #export XDAIS_DIR=~/opt/ti/xdais_m_nn_oo_pp

    After making the changes to setenv, ./prj config runs correctly, is set to use the pre-loaded tools, and the build seems to run successfully.

     

    Regards,

    Lorin