Hi Jimmy,

#1 should be fixed when you run ./ellcc install in the toplevel ellcc directory after you untar the tarball.
#2 was a real problem. I had a bug in the binary distribution script that packaged x86_84 libraries for all the non-x86_64 tarballs. Sorry about that.

You can build compiler-rt by running “scripts/build-compiler-rt -cpCbi”
“cpCbi” means “checkout patch Configure build install”.

I put a prerelease of the next version at http://ellcc.org/prerelease/
Could you give that a try? Unfortunately I don’t have a 64 bit arm system handy.

Thanks for your input!

-Rich

By the way, my Windows version is
Version 6.1 (Build 7601: Service Pack 1)

-Rich

I think that is a great idea. How would you like things to be split up? For example, Just an ARM compiler? No other libraries? What I don’t get is feedback on how people actually use this stuff. Maybe I should set up a way of building a distro that has exactly what people want. Ideas?

-Rich

Hi Stephan,

Yes, that is exactly the problem. After the 0.1.28 version, the config file names were changed, as were the build rules that use them. Unfortunately 0.1.28 was the last successful build of the mingw-w64 tool chain. Something changed in clang or libc++ that causes the clang build to fail. I’ve been trying to figure out what is going wrong, but I haven’t been able to spend a lot of time on it.

Sorry about that. Maybe you could run the Linux version in a virtual machine until a fix is available?

-Rich

Hi Stephan,

I took a quick look at building circle and I was able to build it for the Raspberry Pi 1 and 2 With the following changes to Rules.mk and sample/Rules.mk.
I have not tried to run the final executables, however. The Pi 3 build fails because of assembler weirdness. Maybe modifying the ellcc/libecc/config/arm64v8-linux config file no not use the integrated assembler would help.

I hope this helps.

rich@dev:~/circle$ diff -u -r circle-master circle-master-ellcc/
Only in circle-master-ellcc/: .README.md.swp
diff -u -r circle-master/Rules.mk circle-master-ellcc/Rules.mk
--- circle-master/Rules.mk      2016-10-15 05:45:58.000000000 -0500
+++ circle-master-ellcc/Rules.mk        2016-10-29 15:38:38.023205633 -0500
@@ -24,21 +24,35 @@
 
 -include $(CIRCLEHOME)/Config.mk
 
-RASPPI ?= 1
-PREFIX ?= arm-linux-gnueabihf-
+RASPPI ?= 3
+ELLCC=~/ellcc
+PREFIX ?= $(ELLCC)/bin/
+ELLCCLIBS = $(ELLCC)/libecc/lib/$(TARGET)
 
-CC     = $(PREFIX)gcc
-CPP    = $(PREFIX)g++
+CC     = $(PREFIX)ecc
+CPP    = $(PREFIX)ecc++
 AS     = $(CC)
-LD     = $(PREFIX)ld
-AR     = $(PREFIX)ar
+LD     = $(PREFIX)ecc-ld $(LDFLAGS)
+AR     = $(PREFIX)ecc-ar
+OBJDUMP = $(PREFIX)ecc-objdump
+OBJCOPY = $(PREFIX)ecc-objcopy
+CXXFILT = $(PREFIX)ecc-c++filt
 
 ifeq ($(strip $(RASPPI)),1)
-ARCH   ?= -march=armv6j -mtune=arm1176jzf-s -mfloat-abi=hard 
+TARGET = arm32v6-linux
+ARCH   ?= -target $(TARGET) -march=armv6j -mtune=arm1176jzf-s \
+            -mfloat-abi=soft
+LDFLAGS = -m armelf_linux_eabi -L $(ELLCCLIBS)
 else ifeq ($(strip $(RASPPI)),2)
-ARCH   ?= -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard
+TARGET = arm32v6-linux
+ARCH   ?= -target $(TARGET) -march=armv7-a -mtune=cortex-a7 \
+           -mfpu=neon-vfpv4 -mfloat-abi=soft
+LDFLAGS = -m armelf_linux_eabi -L $(ELLCCLIBS)
 else
-ARCH   ?= -march=armv8-a -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard
+TARGET = arm64v8-linux
+ARCH   ?= -target $(TARGET) -march=armv8-a -mtune=cortex-a53 \
+           -mfpu=neon-fp-armv8 -mfloat-abi=soft
+LDFLAGS = -m aarch64linux -L $(ELLCCLIBS)
 endif
 
 INCLUDE        += -I $(CIRCLEHOME)/include -I $(CIRCLEHOME)/addon -I $(CIRCLEHOME)/app/lib
Only in circle-master-ellcc/: .Rules.mk.swp
diff -u -r circle-master/sample/Rules.mk circle-master-ellcc/sample/Rules.mk
--- circle-master/sample/Rules.mk       2016-10-15 05:45:58.000000000 -0500
+++ circle-master-ellcc/sample/Rules.mk 2016-10-29 15:30:40.785993359 -0500
@@ -27,9 +27,9 @@
 endif
 
 kernel.img: $(OBJS) $(LIBS)
-       $(LD) -o kernel.elf -Map kernel.map -T $(CIRCLEHOME)/circle.ld $(CIRCLEHOME)/lib/startup.o $(OBJS) $(LIBS)
-       $(PREFIX)objdump -d kernel.elf | $(PREFIX)c++filt > kernel.lst
-       $(PREFIX)objcopy kernel.elf -O binary kernel.img
+       $(LD) -o kernel.elf -Map kernel.map -T $(CIRCLEHOME)/circle.ld $(CIRCLEHOME)/lib/startup.o $(OBJS) $(LIBS) -lcompiler-rt
+       $(OBJDUMP) -d kernel.elf | $(CXXFILT) > kernel.lst
+       $(OBJCOPY) kernel.elf -O binary kernel.img
        wc -c kernel.img
 
 include $(CIRCLEHOME)/Rules.mk
rich@dev:~/circle$ 

Hi Alex,

Sorry it has taken so long to get back to you.
I think the problem is that libtool is mistakenly giving the system libexpat.so to the linker when trying to build the metalinkcat utility,

Originally I tried to build ELLCC from scratch on my Fedora system which has libexpat installed. Unfortunately the build went just fine: build with gcc worked, subsequent build with ecc worked. I’m not sure why Ubuntu would be different, unfortunately.

The good news is that you have everything you need built. If you were to edit /home/vagrant/ellcc/libecc/Makefile to remove the libmetalink parts, I think the rest of your build would go OK. Comment this part out:

$(Configs):: musl.install
        $(OUT)$(MAKE) $(MFLAGS) $@.libmetalink.configure && \
        $(MAKE) $(MFLAGS) $@.libmetalink.build && \
        $(MAKE) $(MFLAGS) $@.libmetalink.install

-Rich

Hi Bracket,

Sorry about that. I’ve updated Using ELLCC. I’m also thinking that it might be a good idea to error or warn about a -target option that doesn’t refer to a config file.

-Rich