Quote:
Originally Posted by hippy dave
crap, arm-none-eabi is what i ended up with after following some guide. what would it need to get the right version, different options for the make command maybe?
|
If you followed that guide, look at that "helpful" make file:
Code:
cross-gcc: cross-binutils cross-gcc-first cross-newlib gcc-$(GCC_VERSION)-$(CS_BASE) multilibbash
mkdir -p build/gcc-final && cd build/gcc-final && \
mkdir -p $(PREFIX)/$(TARGET)/usr/include && \
../../gcc-$(GCC_VERSION)-$(CS_BASE)/configure \
--prefix=$(PREFIX) --with-pkgversion=$(PKG_VERSION) \
--with-bugurl=$(BUG_URL) --target=$(TARGET) $(DEPENDENCIES) \
--enable-languages="c,c++" --with-gnu-ld --with-gnu-as \
--with-newlib --disable-nls --disable-libssp \
--disable-shared --enable-threads --with-headers=yes \
--disable-libmudflap --disable-libgomp --enable-lto \
--disable-libstdcxx-pch --enable-poison-system-directories \
--with-sysroot="$(PREFIX)/$(TARGET)" \
--with-build-time-tools="$(PREFIX)/$(TARGET)/bin" \
--enable-extra-sgxxlite-multilibs $(CS_SPECS) && \
$(MAKE) -j$(PROCS) && \
$(MAKE) installdirs install-target && \
$(MAKE) install-gcc
Does that, or does that not say: --with-newlib?
Translation: "newlib" means it is a "standalone" compiler, not a "hosted" compiler for code hosted by an operating system.
Perhaps the description here is clearer:
http://knetconnect.com/KeK/KeK_refer...bsection-B.1.2
Translation:
Change your makefile to build a (e)glibc based compiler not a newlib based compiler.
Note: There are ways to build "hosted" code with a "standalone" compiler but that is far too complicated when you can just build what you need.
Or:
You might want to try crosstool-ng - - I am pretty sure it will run on Mac, check the documentation on their home page.
Or:
Do your builds in Linux VM on your Mac - then you can just use the posted binary tool chains.