8b17219e7d
While you can construct a compile command that does work using the x86_64 host compiler that most people use this is flakey. Different distros handle this is different ways so we default to using a known good i386 compiler via docker. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
38 lines
977 B
Makefile
38 lines
977 B
Makefile
# i386 cross compile notes
|
|
|
|
I386_SRC=$(SRC_PATH)/tests/tcg/i386
|
|
|
|
# Set search path for all sources
|
|
VPATH += $(I386_SRC)
|
|
|
|
I386_SRCS=$(notdir $(wildcard $(I386_SRC)/*.c))
|
|
I386_TESTS=$(I386_SRCS:.c=)
|
|
|
|
# Update TESTS
|
|
TESTS+=$(I386_TESTS)
|
|
|
|
ifneq ($(TARGET_NAME),x86_64)
|
|
CFLAGS+=-m32
|
|
endif
|
|
|
|
#
|
|
# hello-i386 is a barebones app
|
|
#
|
|
hello-i386: CFLAGS+=-ffreestanding
|
|
hello-i386: LDFLAGS+=-nostdlib
|
|
|
|
#
|
|
# test-386 includes a couple of additional objects that need to be linked together
|
|
#
|
|
|
|
test-i386: test-i386.c test-i386-code16.S test-i386-vm86.S test-i386.h test-i386-shift.h test-i386-muldiv.h
|
|
$(CC) $(CFLAGS) $(LDFLAGS) -o $@ \
|
|
$(<D)/test-i386.c $(<D)/test-i386-code16.S $(<D)/test-i386-vm86.S -lm
|
|
|
|
# Specialist test runners
|
|
run-runcom: runcom pi_10.com
|
|
$(call quiet-command, $(QEMU) ./runcom $(I386_SRC)/pi_10.com > runcom.out, "TEST", "$< on $(TARGET_NAME)")
|
|
|
|
# On i386 and x86_64 Linux only supports 4k pages (large pages are a different hack)
|
|
EXTRA_RUNS+=run-test-mmap-4096
|