GNU Arm Embedded Toolchain

Where Oh Where Could My Libraries Be?

Asked by Vince

I am running Debian Jessie (testing). I installed the following packages:

$ dpkg -l | grep arm-
ii binutils-arm-none-eabi 2.24-2+4 amd64 GNU assembler, linker and binary utilities for ARM Cortex-A/R/M processors
ii gcc-arm-none-eabi 4.8.2-12+5 amd64 GCC cross compiler for ARM Cortex-A/R/M processors

However, I am unable to compile with arm-none-eabi-gcc as arm-none-eabi-ld cannot find the applicable libraries:

$ arm-none-eabi-gcc test.c
/usr/bin/arm-none-eabi-ld: cannot find crt0.o: No such file or directory
/usr/bin/arm-none-eabi-ld: cannot find -lc
collect2: error: ld returned 1 exit status

The libnewlib-arm-none-eabi package appears to include the applicable files (i.e., crt0.o), but this package is only available for Debian Sid (unstable). So is GNU cross compilation not supported under Debian Jessie (testing)? If that is the case then why are the gcc-arm-none-eabi and binutils-arm-none-eabi packages available? Thanks in advance for your help!

Question information

Language:
English Edit question
Status:
Answered
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Terry Guo (terry.guo) said : 		#1

It seems to me that you are using tool chain made from Debian release itself. Currently we don't provide tool chain for being released with Debian. The only way to use our tool chain under Debian is to download the bz2 package and decompress it in a proper place, then you are good to go. And our tool chain just focus on R/M, not including A.

Revision history for this message
Terry Guo (terry.guo) said : 		#2

To be precise, you can use our tool chain to generate code for A profile bare metal. But the linked Multilibs are general libraries, unlike the M profiles which have dedicated Multilibs.

Can you help with this problem?

Provide an answer of your own, or ask Vince for more information if necessary.

To post a message you must log in.