top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

PIC 4.7 & 4.8 gcc libraries for arm

+2 votes
198 views

I would like to build position-independent 4.7 and 4.8 gcc libraries for host: mac target: arm-none-eabi.

Do anyone has instructions for achieving this?

posted Aug 8, 2013 by Luv Kumar

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote
trouble building gcc 4.7.2 w/binutils 2.23.1

I'm trying to build GCC 4.7.2 with binutils 2.23.1 and am getting a compile error:

dwarf.o: In function get_TAG_name': /w/umoszkow/gcc/x86_64/binutils/../../gcc-4.7.2/binutils/dwarf.c:662: undefined reference toget_DW_TAG_name'
dwarf.o: In function get_FORM_name': /w/umoszkow/gcc/x86_64/binutils/../../gcc-4.7.2/binutils/dwarf.c:678: undefined reference toget_DW_FORM_name' dwarf.o: In function get_AT_name': /w/umoszkow/gcc/x86_64/binutils/../../gcc-4.7.2/binutils/dwarf.c:1867: undefined reference toget_DW_AT_name'
collect2: error: ld returned 1 exit status

Any idea how to get around this build problem? My arch is x86_64 and my OS is RHEL4u8WS.

+1 vote
gcc 4.8++ neglect my terminfo

With the apparition of colorification of gcc diag message, it sounds like the color are hard coded to who knows terminals.

I Know that I can use option/env to remove color, yet when non prepared for it, it crash my terminal ( that is not vt100 or whatever xterm is).

My TERM var is properly setup up though. Is that expected behavior?

I know that colorisation is a rampant disease with ls, grep etc, with default color barely readable imposing painful customization time at moment you would like to spend your time to other duties :)

Would'nt be possible to have color only if some ENV are already set, i.e gcc could detect in the env that the user is a *COLOR* officionado and colorify then, instead of imposing regression in both terminal non xterm, and regression on diag parser that discover with horror this new escape sequence in the output :)

+2 votes
gcc v4.7 build errors on Android Jellybean

we are trying to compile Android Jellybean (JB43) and It uses Toolchain GCC 4.7 with this toolchain we are seeing this error:

Error: selected processor does not support requested special purpose register -- `mrs r5,FPEXC

Is there a way to fix this. I use arm v7-a

0 votes
Installing GCC on Windows Environment (WIN 8)

Last time I asked GCC installation and it was very helpful. Can someone point me how to achieve it on Windows?

+3 votes
Problem build gcc 5.1 with openacc support for nvptx

I am following instructions from
https://gcc.gnu.org/wiki/Offloading

I'm using the configure line for Nvidia ptx. The build stops in configuring nvptx-none/libgfortran with error:

checking whether symbol versioning is supported... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.

My host OS is CentOS 6.5. I'm using gcc 4.7 (built with system gcc 4.4) to build gcc 5.1

Can someone give me hint to look where the problem could come from ?

...