eLua Development

arm-none-eabi-cc: command not found

classic Classic list List threaded Threaded
♦
♦
 5 messages Options
james osburn james osburn
Reply | Threaded
Open this post in threaded view
♦
♦
|

arm-none-eabi-cc: command not found

Is it appropriate to ask this mail list about building the cross compiler for the arm-none-eabi toolchain?
james

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
jbsnyder jbsnyder
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: arm-none-eabi-cc: command not found

On Sun, Nov 13, 2011 at 5:56 PM, james osburn <[hidden email]> wrote:
> Is it appropriate to ask this mail list about building the cross compiler
> for the arm-none-eabi toolchain?

I think it's perfectly reasonable as long as the list doesn't end up
solely answering questions about cross-compiling toolchains.  We do,
after all, provide some form of instructions on how to build them and
various community members have provided scripts, makefiles and howtos
(myself included: https://github.com/jsnyder/arm-eabi-toolchain).

Which instructions or scripts are you using to do the build?

If your subject is a hint, I suspect you got through some number of
stages of the build and it may have failed in newlib? or something
like that? Usually one gets errors like that if the cross compiling
gcc that one has just built and installed into a new path is not in
the binary search path (PATH) when configure ran for the stage of the
build you're in if I recall.  Depending on which instructions you're
using and what actual stage you're at, there might be a different best
recommendation, but certainly make sure that whatever shell you're
doing the build from includes the path where arm-none-eabi-gcc will
end up, precreate that bin directory if it doesn't already exist
before you set path, i.e.:

mkdir -p $PREFIX/bin
export PATH=$PREFIX/bin:$PATH
(where $PREFIX is the install prefix used by the scripts you're using)

and then at least redo the configure, then continue building at the
stage where things stoppped for you.

> james
>
> _______________________________________________
> eLua-dev mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/elua-dev
>
>
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
james osburn james osburn
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: arm-none-eabi-cc: command not found

here is where i get to after:
mkdir -p $HOME/arm-cs-tools/bin
export PATH=$HOME/arm-cs-tools/bin:$PATH
and then
make install-cross
it runs for a while and then:

arm-none-eabi-cc -B/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/ -isystem /home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/targ-include -isystem /home/elua/programming/arm-eabi-toolchain/newlib-2011.03/newlib/libc/include    -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" -DPACKAGE_VERSION=\"1.18.0\" -DPACKAGE_STRING=\"newlib\ 1.18.0\" -DPACKAGE_BUGREPORT=\"\" -I. -I../../../../../../newlib-2011.03/newlib/libc/argz -D__NO_SYSCALLS__ -DHAVE_RENAME -DHAVE_SYSTEM -fno-builtin      -ffunction-sections -fdata-sections -DPREFER_SIZE_OVER_SPEED -D__OPTIMIZE_SIZE__ -Os -fomit-frame-pointer -fno-unroll-loops -D__BUFSIZ__=256 -mabi=aapcs -c -o lib_a-argz_append.o `test -f 'argz_append.c' || echo '../../../../../../newlib-2011.03/newlib/libc/argz/'`argz_append.c
/bin/sh: arm-none-eabi-cc: command not found
make[6]: *** [lib_a-dummy.o] Error 127
make[6]: *** Waiting for unfinished jobs....
/bin/sh: arm-none-eabi-cc: command not found
make[6]: *** [lib_a-argz_add.o] Error 127
/bin/sh: arm-none-eabi-cc: command not found
make[6]: *** [lib_a-argz_add_sep.o] Error 127
/bin/sh: arm-none-eabi-cc: command not found
make[6]: *** [lib_a-argz_append.o] Error 127
make[6]: Leaving directory `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/libc/argz'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/libc'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib'
make[2]: *** [all-target-newlib] Error 2
make[2]: Leaving directory `/home/elua/programming/arm-eabi-toolchain/build/newlib'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/elua/programming/arm-eabi-toolchain/build/newlib'
make: *** [cross-newlib] Error 2
rm arm-2011.03-42-arm-none-eabi/binutils-2011.03-42.tar.bz2 arm-2011.03-42-arm-none-eabi/newlib-2011.03-42.tar.bz2
[elua@localhost arm-eabi-toolchain]$


On Sun, Nov 13, 2011 at 6:09 PM, James Snyder <[hidden email]> wrote:
On Sun, Nov 13, 2011 at 5:56 PM, james osburn <[hidden email]> wrote:
> Is it appropriate to ask this mail list about building the cross compiler
> for the arm-none-eabi toolchain?

I think it's perfectly reasonable as long as the list doesn't end up
solely answering questions about cross-compiling toolchains.  We do,
after all, provide some form of instructions on how to build them and
various community members have provided scripts, makefiles and howtos
(myself included: https://github.com/jsnyder/arm-eabi-toolchain).

Which instructions or scripts are you using to do the build?

If your subject is a hint, I suspect you got through some number of
stages of the build and it may have failed in newlib? or something
like that? Usually one gets errors like that if the cross compiling
gcc that one has just built and installed into a new path is not in
the binary search path (PATH) when configure ran for the stage of the
build you're in if I recall.  Depending on which instructions you're
using and what actual stage you're at, there might be a different best
recommendation, but certainly make sure that whatever shell you're
doing the build from includes the path where arm-none-eabi-gcc will
end up, precreate that bin directory if it doesn't already exist
before you set path, i.e.:

mkdir -p $PREFIX/bin
export PATH=$PREFIX/bin:$PATH
(where $PREFIX is the install prefix used by the scripts you're using)

and then at least redo the configure, then continue building at the
stage where things stoppped for you.

> james
>
> _______________________________________________
> eLua-dev mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/elua-dev
>
>
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev


_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
jbsnyder jbsnyder
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: arm-none-eabi-cc: command not found

If you're trying this on top of a previous attempt, you may want to
make sure you do a "make clean" first, if you aren't doing that.

Also, is "arm-none-eabi-gcc" in your path after you add
$HOME/arm-cs-tools/bin to your path?



On Sun, Nov 13, 2011 at 8:24 PM, james osburn <[hidden email]> wrote:

> here is where i get to after:
> mkdir -p $HOME/arm-cs-tools/bin
> export PATH=$HOME/arm-cs-tools/bin:$PATH
> and then
> make install-cross
>
> it runs for a while and then:
>
> arm-none-eabi-cc
> -B/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/
> -isystem
> /home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/targ-include
> -isystem
> /home/elua/programming/arm-eabi-toolchain/newlib-2011.03/newlib/libc/include
> -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\"
> -DPACKAGE_VERSION=\"1.18.0\" -DPACKAGE_STRING=\"newlib\ 1.18.0\"
> -DPACKAGE_BUGREPORT=\"\" -I.
> -I../../../../../../newlib-2011.03/newlib/libc/argz -D__NO_SYSCALLS__
> -DHAVE_RENAME -DHAVE_SYSTEM -fno-builtin      -ffunction-sections
> -fdata-sections -DPREFER_SIZE_OVER_SPEED -D__OPTIMIZE_SIZE__ -Os
> -fomit-frame-pointer -fno-unroll-loops -D__BUFSIZ__=256 -mabi=aapcs -c -o
> lib_a-argz_append.o `test -f 'argz_append.c' || echo
> '../../../../../../newlib-2011.03/newlib/libc/argz/'`argz_append.c
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-dummy.o] Error 127
> make[6]: *** Waiting for unfinished jobs....
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-argz_add.o] Error 127
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-argz_add_sep.o] Error 127
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-argz_append.o] Error 127
> make[6]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/libc/argz'
> make[5]: *** [all-recursive] Error 1
> make[5]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/libc'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib'
> make[2]: *** [all-target-newlib] Error 2
> make[2]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib'
> make: *** [cross-newlib] Error 2
> rm arm-2011.03-42-arm-none-eabi/binutils-2011.03-42.tar.bz2
> arm-2011.03-42-arm-none-eabi/newlib-2011.03-42.tar.bz2
> [elua@localhost arm-eabi-toolchain]$
>
>
> On Sun, Nov 13, 2011 at 6:09 PM, James Snyder <[hidden email]>
> wrote:
>>
>> On Sun, Nov 13, 2011 at 5:56 PM, james osburn <[hidden email]> wrote:
>> > Is it appropriate to ask this mail list about building the cross
>> > compiler
>> > for the arm-none-eabi toolchain?
>>
>> I think it's perfectly reasonable as long as the list doesn't end up
>> solely answering questions about cross-compiling toolchains.  We do,
>> after all, provide some form of instructions on how to build them and
>> various community members have provided scripts, makefiles and howtos
>> (myself included: https://github.com/jsnyder/arm-eabi-toolchain).
>>
>> Which instructions or scripts are you using to do the build?
>>
>> If your subject is a hint, I suspect you got through some number of
>> stages of the build and it may have failed in newlib? or something
>> like that? Usually one gets errors like that if the cross compiling
>> gcc that one has just built and installed into a new path is not in
>> the binary search path (PATH) when configure ran for the stage of the
>> build you're in if I recall.  Depending on which instructions you're
>> using and what actual stage you're at, there might be a different best
>> recommendation, but certainly make sure that whatever shell you're
>> doing the build from includes the path where arm-none-eabi-gcc will
>> end up, precreate that bin directory if it doesn't already exist
>> before you set path, i.e.:
>>
>> mkdir -p $PREFIX/bin
>> export PATH=$PREFIX/bin:$PATH
>> (where $PREFIX is the install prefix used by the scripts you're using)
>>
>> and then at least redo the configure, then continue building at the
>> stage where things stoppped for you.
>>
>> > james
>> >
>> > _______________________________________________
>> > eLua-dev mailing list
>> > [hidden email]
>> > https://lists.berlios.de/mailman/listinfo/elua-dev
>> >
>> >
>> _______________________________________________
>> eLua-dev mailing list
>> [hidden email]
>> https://lists.berlios.de/mailman/listinfo/elua-dev
>
>
> _______________________________________________
> eLua-dev mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/elua-dev
>
>
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
james osburn james osburn
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: arm-none-eabi-cc: command not found

I actually removed the whole source tree and started over.
By that i removed $/arm-cs-tools
and rm -rf /home/elua/programming/arm-eabi-toolchain,
Then re-git cloned the sources in a fresh shell.
But that is a good point.

James
On Sun, Nov 13, 2011 at 8:30 PM, James Snyder <[hidden email]> wrote:
If you're trying this on top of a previous attempt, you may want to
make sure you do a "make clean" first, if you aren't doing that.

Also, is "arm-none-eabi-gcc" in your path after you add
$HOME/arm-cs-tools/bin to your path?



On Sun, Nov 13, 2011 at 8:24 PM, james osburn <[hidden email]> wrote:
> here is where i get to after:
> mkdir -p $HOME/arm-cs-tools/bin
> export PATH=$HOME/arm-cs-tools/bin:$PATH
> and then
> make install-cross
>
> it runs for a while and then:
>
> arm-none-eabi-cc
> -B/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/
> -isystem
> /home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/targ-include
> -isystem
> /home/elua/programming/arm-eabi-toolchain/newlib-2011.03/newlib/libc/include
> -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\"
> -DPACKAGE_VERSION=\"1.18.0\" -DPACKAGE_STRING=\"newlib\ 1.18.0\"
> -DPACKAGE_BUGREPORT=\"\" -I.
> -I../../../../../../newlib-2011.03/newlib/libc/argz -D__NO_SYSCALLS__
> -DHAVE_RENAME -DHAVE_SYSTEM -fno-builtin      -ffunction-sections
> -fdata-sections -DPREFER_SIZE_OVER_SPEED -D__OPTIMIZE_SIZE__ -Os
> -fomit-frame-pointer -fno-unroll-loops -D__BUFSIZ__=256 -mabi=aapcs -c -o
> lib_a-argz_append.o `test -f 'argz_append.c' || echo
> '../../../../../../newlib-2011.03/newlib/libc/argz/'`argz_append.c
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-dummy.o] Error 127
> make[6]: *** Waiting for unfinished jobs....
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-argz_add.o] Error 127
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-argz_add_sep.o] Error 127
> /bin/sh: arm-none-eabi-cc: command not found
> make[6]: *** [lib_a-argz_append.o] Error 127
> make[6]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/libc/argz'
> make[5]: *** [all-recursive] Error 1
> make[5]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib/libc'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib/arm-none-eabi/newlib'
> make[2]: *** [all-target-newlib] Error 2
> make[2]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory
> `/home/elua/programming/arm-eabi-toolchain/build/newlib'
> make: *** [cross-newlib] Error 2
> rm arm-2011.03-42-arm-none-eabi/binutils-2011.03-42.tar.bz2
> arm-2011.03-42-arm-none-eabi/newlib-2011.03-42.tar.bz2
> [elua@localhost arm-eabi-toolchain]$
>
>
> On Sun, Nov 13, 2011 at 6:09 PM, James Snyder <[hidden email]>
> wrote:
>>
>> On Sun, Nov 13, 2011 at 5:56 PM, james osburn <[hidden email]> wrote:
>> > Is it appropriate to ask this mail list about building the cross
>> > compiler
>> > for the arm-none-eabi toolchain?
>>
>> I think it's perfectly reasonable as long as the list doesn't end up
>> solely answering questions about cross-compiling toolchains.  We do,
>> after all, provide some form of instructions on how to build them and
>> various community members have provided scripts, makefiles and howtos
>> (myself included: https://github.com/jsnyder/arm-eabi-toolchain).
>>
>> Which instructions or scripts are you using to do the build?
>>
>> If your subject is a hint, I suspect you got through some number of
>> stages of the build and it may have failed in newlib? or something
>> like that? Usually one gets errors like that if the cross compiling
>> gcc that one has just built and installed into a new path is not in
>> the binary search path (PATH) when configure ran for the stage of the
>> build you're in if I recall.  Depending on which instructions you're
>> using and what actual stage you're at, there might be a different best
>> recommendation, but certainly make sure that whatever shell you're
>> doing the build from includes the path where arm-none-eabi-gcc will
>> end up, precreate that bin directory if it doesn't already exist
>> before you set path, i.e.:
>>
>> mkdir -p $PREFIX/bin
>> export PATH=$PREFIX/bin:$PATH
>> (where $PREFIX is the install prefix used by the scripts you're using)
>>
>> and then at least redo the configure, then continue building at the
>> stage where things stoppped for you.
>>
>> > james
>> >
>> > _______________________________________________
>> > eLua-dev mailing list
>> > [hidden email]
>> > https://lists.berlios.de/mailman/listinfo/elua-dev
>> >
>> >
>> _______________________________________________
>> eLua-dev mailing list
>> [hidden email]
>> https://lists.berlios.de/mailman/listinfo/elua-dev
>
>
> _______________________________________________
> eLua-dev mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/elua-dev
>
>
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev


_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev
Free forum by Nabble Edit this page