build issues on OSX

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

willem itsme at xs4all.nl
Sun Mar 21 20:29:05 UTC 2010


On 2010-03-14 13:15:00, Nathan Fain wrote:
> On Sun, 14 Mar 2010 13:12:10 +0100, Sylvain Munaut <246tnt at gmail.com>
> wrote:
>   
>> I think you're right. Look in firmware/Makefile.inc line 118
>>
>> It should probably be
>>
>>     $(CROSS_COMPILE)$(AR) cru $$($(1)_DIR)/lib$(1).a $$($(1)_OBJS)
>>
>> instead of just:
>>
>>     $(AR) cru $$($(1)_DIR)/lib$(1).a $$($(1)_OBJS)
>>     
> definitely the more intelligent solution, rather than what I just sent. 
> thanks :)
>   
another solution:

the macports arm-elf-binutils package installs all tools with arm-elf
prefix, while the target configure script expects arm-elf-linux.

in the toplevel Makefile there is an explicit override of CC with
arm-elf-gcc
all the other tools are searched for with the 'arm-elf-linux-' prefix.

also note this warning in the configure output:
======
configure: WARNING: using cross tools not prefixed with host triplet
======

two possible solutions:

1) add symlinks with the arm-elf-linux for all relevant binaries.

for i in strip objdump ar ranlib; do ln -sf $(dirname $(which
arm-elf-gcc))/arm-elf-$i ~/bin/arm-elf-linux-$i; done

2) add more overrides to the target configure line

   RANLIB="$(CROSS_TOOL_PREFIX)ranlib"
OBJDUMP="$(CROSS_TOOL_PREFIX)objdump" AR="$(CROSS_TOOL_PREFIX)ar"
STRIP="$(CROSS_TOOL_PREFIX

willem





More information about the baseband-devel mailing list