rust/tests/run-make/issue-36710/Makefile

# ignore-none no-std is not supported
# ignore-wasm32 FIXME: don't attempt to compile C++ to WASM
# ignore-wasm64 FIXME: don't attempt to compile C++ to WASM
# ignore-nvptx64-nvidia-cuda FIXME: can't find crate for `std`
# ignore-musl FIXME: this makefile needs teaching how to use a musl toolchain
#                    (see dist-i586-gnu-i586-i686-musl Dockerfile)

include ../../run-make-fulldeps/tools.mk

all: foo
	$(call RUN,foo)

foo: foo.rs $(call NATIVE_STATICLIB,foo)
	$(RUSTC) $< -lfoo $(EXTRARSCXXFLAGS) --target $(TARGET)

$(TMPDIR)/libfoo.o: foo.cpp
	$(call COMPILE_OBJ_CXX,$@,$<)
test: run-make: flag tests which won't work in no-std environments 2021-03-15 13:00:14 -05:00			`# ignore-none no-std is not supported`
Revert "test: run-make: skip when cross-compiling" This reverts commit 0567fec8e47f83ddda623f93deccddddd3f6744f. 2022-10-18 02:47:55 -05:00			`# ignore-wasm32 FIXME: don't attempt to compile C++ to WASM`
			`# ignore-wasm64 FIXME: don't attempt to compile C++ to WASM`
			# ignore-nvptx64-nvidia-cuda FIXME: can't find crate for `std`
test: run-make: skip tests on unsupported platforms The tests issue-36710 and incr-prev-body-beyond-eof were changed in a previous commit so that the correct target was passed to rustc (previously rustc was building for the host not for the specific target). Since that change it turns out that these platforms never worked (they only appeared to work because rustc was actually building for the host architecture). The wasm architectures fall over trying to build the C++ file in issue-36710. They look for clang (which isn't installed in the test-various docker container). If clang is installed, they can't find a wasm c++ standard library to link to. nvtptx64-nvidia-cuda fails in rustc saying it can't find std. The rust platforms support page says that std is supported on cuda so this is surprising. dist-i586-gnu-i586-i686-musl can't find the C++ compiler. There is only a musl-gcc and no musl-g++ in /musl-i586/bin/. The Docker image probably needs tweaking. 2021-03-16 13:22:21 -05:00			`# ignore-musl FIXME: this makefile needs teaching how to use a musl toolchain`
			`# (see dist-i586-gnu-i586-i686-musl Dockerfile)`
run-make: skip issue-36710 on riscv64 and armhf The test assumes it can run target binaries on the host. This not true for riscv64 CI (or for other platforms using remote-test-server). 2021-01-11 12:24:54 -06:00
Move issue-36710 test to run-make Somewhat hacky to reuse `tools.mk` like this, we should probably migrate most of them now 2020-10-14 07:29:57 -05:00			`include ../../run-make-fulldeps/tools.mk`
Add a test for issue 36710. This still expectedly fails for musl targets with +crt-static. 2018-05-02 03:26:00 -05:00
use ignore directives for run-make tests This makes the tests easier to read, and makes it possible to tell which tests aren't being run on the host platform. Fixes #56704. 2019-01-06 15:27:57 -06:00			`all: foo`
Add a test for issue 36710. This still expectedly fails for musl targets with +crt-static. 2018-05-02 03:26:00 -05:00			`$(call RUN,foo)`

			`foo: foo.rs $(call NATIVE_STATICLIB,foo)`
run-make: Specify --target to rustc Resolves #78911 The target's linker was used but rustc wasn't told to build for that target (instead defaulting to the host). This led to the host instead of the target getting tested and to the linker getting inappropriate arguments. 2021-01-09 16:54:21 -06:00			`$(RUSTC) $< -lfoo $(EXTRARSCXXFLAGS) --target $(TARGET)`
Add a test for issue 36710. This still expectedly fails for musl targets with +crt-static. 2018-05-02 03:26:00 -05:00
			`$(TMPDIR)/libfoo.o: foo.cpp`
			`$(call COMPILE_OBJ_CXX,$@,$<)`