This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: why there are two executable gcc in my arm cross tool chain?
- From: Terry Guo <flameroc at gmail dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: gcc <gcc-help at gcc dot gnu dot org>
- Date: Tue, 29 Oct 2013 11:30:00 +0800
- Subject: Re: why there are two executable gcc in my arm cross tool chain?
- Authentication-results: sourceware.org; auth=none
- References: <CAGbRaL4k-PxcX7ybGVb078kJVL0B+CGqH2LXfNYa3wobj_RW5w at mail dot gmail dot com> <CAKOQZ8z1c91CZ5Yoo6jRGOhqbTaAMLC33yh=3y7SEsK0c7ZLag at mail dot gmail dot com>
On Tue, Oct 29, 2013 at 10:47 AM, Ian Lance Taylor <iant@google.com> wrote:
> On Mon, Oct 28, 2013 at 7:07 PM, Terry Guo <flameroc@gmail.com> wrote:
>>
>> I cross build a tool chain for arm-none-eabi targets and find there
>> are some executable files under folder:
>>
>> arm-none-eabi/bin/
>> âââ ar
>> âââ as
>> âââ c++
>> âââ g++
>> âââ gcc
>> âââ ld
>> âââ ld.bfd
>> âââ nm
>> âââ objcopy
>> âââ objdump
>> âââ ranlib
>> âââ strip
>
> These executables are used by the GCC binary and associated tools
> internally when they need to invoke other executables. The directory
> exists so that the tools can reliably find the executable to run
> without having to worry about the exact name.
>
> If you run "make install" the identical executables will be symlinked
> together so no disk space is wasted. Of course this fails under
> various distribution mechanisms.
>
>
>> While similar files under folder:
>> bin
>> âââ arm-none-eabi-addr2line
>> âââ arm-none-eabi-ar
>> âââ arm-none-eabi-as
>> âââ arm-none-eabi-c++
>> âââ arm-none-eabi-c++filt
>> âââ arm-none-eabi-cpp
>> âââ arm-none-eabi-elfedit
>> âââ arm-none-eabi-g++
>> âââ arm-none-eabi-gcc
>> âââ arm-none-eabi-gcc-4.7.4
>> âââ arm-none-eabi-gcc-ar
>> âââ arm-none-eabi-gcc-nm
>> âââ arm-none-eabi-gcc-ranlib
>> âââ arm-none-eabi-gcov
>> âââ arm-none-eabi-gdb
>> âââ arm-none-eabi-gdbtui
>> âââ arm-none-eabi-gprof
>> âââ arm-none-eabi-ld
>> âââ arm-none-eabi-ld.bfd
>> âââ arm-none-eabi-nm
>> âââ arm-none-eabi-objcopy
>> âââ arm-none-eabi-objdump
>> âââ arm-none-eabi-ranlib
>> âââ arm-none-eabi-readelf
>> âââ arm-none-eabi-size
>> âââ arm-none-eabi-strings
>> âââ arm-none-eabi-strip
>
> These executables are intended for the user to run.
>
> Ian
Thank you Ian. I got it now.
BR,
Terry