Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 17 of 17
Like Tree5Likes
You need to edit the your bashrc and add the path of toolchain. export GNU_ARM = 'CodeSourcery/ your complete path here /bin' and there will be a line with $PATH ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Apr 2012
    Posts
    23

    You need to edit the your bashrc and add the path of toolchain.
    export GNU_ARM = 'CodeSourcery/ your complete path here /bin'
    and there will be a line with $PATH add $GNU_ARM to it , I think its like $PATH:$GNU_ARM, then do source ~/.bashrc , also add this to the root user bashrc .

  2. #12
    Just Joined!
    Join Date
    Aug 2012
    Posts
    19
    Quote Originally Posted by kartikkg View Post
    You need to edit the your bashrc and add the path of toolchain.
    export GNU_ARM = 'CodeSourcery/ your complete path here /bin'
    and there will be a line with $PATH add $GNU_ARM to it , I think its like $PATH:$GNU_ARM, then do source ~/.bashrc , also add this to the root user bashrc .
    thanks man. what about this error: (did these things you say were about this?)
    Code:
    In file included from arch/arm/mach-msm/board-es209ra.c:108:0:
    include/linux/usb/android.h:47:8: error: redefinition of 'struct usb_composition'
    arch/arm/mach-msm/include/mach/msm_hsusb.h:54:8: note: originally defined here
    make[1]: *** [arch/arm/mach-msm/board-es209ra.o] Error 1
    make: *** [arch/arm/mach-msm] Error 2
    I played with cods several times but no luck ever

  3. #13
    Just Joined!
    Join Date
    Apr 2012
    Posts
    23
    Can you give me the link to the kernel source and the list of all the commands you are using to build it ?
    amin021023 likes this.

  4. $spacer_open
    $spacer_close
  5. #14
    Just Joined!
    Join Date
    Aug 2012
    Posts
    19
    Quote Originally Posted by kartikkg View Post
    Can you give me the link to the kernel source and the list of all the commands you are using to build it ?
    I could kiss you. here we go:

    the source and files mentioned in the error:

    msm_hsusb.h :
    Code:
    https://github.com/freexperia/semc-kernel-qsd8k-ics/blob/master/arch/arm/mach-msm/include/mach/msm_hsusb.h
    android.h :
    Code:
    https://github.com/freexperia/semc-kernel-qsd8k-ics/blob/master/include/linux/usb/android.h
    my opinion: because of this cod Implement twice in above files we get the error:
    Code:
    struct usb_composition {
    	__u16   product_id;
    	unsigned long functions;
    check out the lines 54 and 48 you'll see. but I played with the cods several times such as removing , replacing but each time got another error....Is it possible that we force compiler just ignore the issue during process or something?


    the commands I use for compile:
    Code:
    $ export ARCH=arm 
    $ export CROSS_COMPILE=~/android/kernel/toolchains/arm-eabi-linaro-4.6.2/bin/arm-eabi-
    $ make fxp_es209ra_defconfig
    $ make -j1
    RESCUE ME!!!!!
    Last edited by amin021023; 08-27-2012 at 07:57 AM.

  6. #15
    Just Joined!
    Join Date
    Apr 2012
    Posts
    23
    I downloaded it and tried , it compiled fine , it built zimage , vmlinux . Uimage didnt get built but I think thats not the main issue. Here is what I did.
    Removed 2 lines which had werror in Makefile and used the following commands.
    Code:
    make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- fxp_es209ra_defconfig
    Code:
    make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
    it built fine .
    I suggest you to uncompress the kernel in a new dir and follow the above steps to get it built.
    amin021023 likes this.

  7. #16
    Just Joined!
    Join Date
    Aug 2012
    Posts
    19
    Quote Originally Posted by kartikkg View Post
    I downloaded it and tried , it compiled fine , it built zimage , vmlinux . Uimage didnt get built but I think thats not the main issue. Here is what I did.
    Removed 2 lines which had werror in Makefile and used the following commands.
    Code:
    make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- fxp_es209ra_defconfig
    Code:
    make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
    it built fine .
    I suggest you to uncompress the kernel in a new dir and follow the above steps to get it built.
    I tried but it says "arm-none-linux-gnueabi-gcc: not found" I know as you said before I should do change into bashrc file but I prefer to use this versian of toolchain specially for android and I already got it working:
    Code:
    https://github.com/DooMLoRD/android_prebuilt_toolchains
    now I think I have two options: (correct me if I'm wrong)

    1.do bashrc file and get "arm-none-linux-gnueab" to work >>>but I couldn't understand some parts of your guide few Previous posts>>>I'll give you my bashrc file if you please do changes for me I'll be thankfull

    2. compile with android_prebuilt_toolchains that I already got it working but the problem is I get error with it so there is only option one

    this is my bashrc file:
    Code:
    # ~/.bashrc: executed by bash(1) for non-login shells.
    # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
    # for examples
    
    # If not running interactively, don't do anything
    [ -z "$PS1" ] && return
    
    # don't put duplicate lines or lines starting with space in the history.
    # See bash(1) for more options
    HISTCONTROL=ignoreboth
    
    # append to the history file, don't overwrite it
    shopt -s histappend
    
    # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
    HISTSIZE=1000
    HISTFILESIZE=2000
    
    # check the window size after each command and, if necessary,
    # update the values of LINES and COLUMNS.
    shopt -s checkwinsize
    
    # If set, the pattern "**" used in a pathname expansion context will
    # match all files and zero or more directories and subdirectories.
    #shopt -s globstar
    
    # make less more friendly for non-text input files, see lesspipe(1)
    [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
    
    # set variable identifying the chroot you work in (used in the prompt below)
    if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
        debian_chroot=$(cat /etc/debian_chroot)
    fi
    
    # set a fancy prompt (non-color, unless we know we "want" color)
    case "$TERM" in
        xterm-color) color_prompt=yes;;
    esac
    
    # uncomment for a colored prompt, if the terminal has the capability; turned
    # off by default to not distract the user: the focus in a terminal window
    # should be on the output of commands, not on the prompt
    #force_color_prompt=yes
    
    if [ -n "$force_color_prompt" ]; then
        if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    	# We have color support; assume it's compliant with Ecma-48
    	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    	# a case would tend to support setf rather than setaf.)
    	color_prompt=yes
        else
    	color_prompt=
        fi
    fi
    
    if [ "$color_prompt" = yes ]; then
        PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
    else
        PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
    fi
    unset color_prompt force_color_prompt
    
    # If this is an xterm set the title to user@host:dir
    case "$TERM" in
    xterm*|rxvt*)
        PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
        ;;
    *)
        ;;
    esac
    
    # enable color support of ls and also add handy aliases
    if [ -x /usr/bin/dircolors ]; then
        test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
        alias ls='ls --color=auto'
        #alias dir='dir --color=auto'
        #alias vdir='vdir --color=auto'
    
        alias grep='grep --color=auto'
        alias fgrep='fgrep --color=auto'
        alias egrep='egrep --color=auto'
    fi
    
    # some more ls aliases
    alias ll='ls -alF'
    alias la='ls -A'
    alias l='ls -CF'
    
    # Add an "alert" alias for long running commands.  Use like so:
    #   sleep 10; alert
    alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
    
    # Alias definitions.
    # You may want to put all your additions into a separate file like
    # ~/.bash_aliases, instead of adding them here directly.
    # See /usr/share/doc/bash-doc/examples in the bash-doc package.
    
    if [ -f ~/.bash_aliases ]; then
        . ~/.bash_aliases
    fi
    
    # enable programmable completion features (you don't need to enable
    # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
    # sources /etc/bash.bashrc).
    if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
        . /etc/bash_completion
    fi
    
    PATH=$PATH:/SDK_PATH/tools/
    export PATH
    
    # Android tools
    export PATH=${PATH}:~/android-sdk/tools
    export PATH=${PATH}:~/android-sdk/platform-tools
    export PATH=${PATH}:~/bin
    alias subtitlefixer=~/.local/bin/SubtitleFixer/SubtitleFixer

  8. #17
    Just Joined!
    Join Date
    Aug 2012
    Posts
    19
    get tis error:

    Code:
    make: arm-none-linux-gnueabi-gcc: Command not found
      CHK     include/linux/version.h
    make[1]: `include/asm-arm/mach-types.h' is up to date.
      CHK     include/linux/utsrelease.h
      SYMLINK include/asm -> include/asm-arm
      CC      kernel/bounds.s
    /bin/sh: 1: arm-none-linux-gnueabi-gcc: not found
    make[1]: *** [kernel/bounds.s] Error 127
    make: *** [prepare0] Error 2

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •