os-rust/tests/run-make/use-extern-for-plugins/Makefile

include ../tools.mk

# ignore-freebsd
# ignore-openbsd
# ignore-solaris

HOST := $(shell $(RUSTC) -vV | grep 'host:' | sed 's/host: //')
ifeq ($(findstring i686,$(HOST)),i686)
TARGET := $(subst i686,x86_64,$(HOST))
else
TARGET := $(subst x86_64,i686,$(HOST))
endif

all:
	$(RUSTC) foo.rs -C extra-filename=-host
	$(RUSTC) bar.rs -C extra-filename=-targ --target $(TARGET)
	$(RUSTC) baz.rs --extern a=$(TMPDIR)/liba-targ.rlib --target $(TARGET)
Diagnose missing includes in run-make tests 2022-08-23 00:00:00 +00:00			`include ../tools.mk`
rustc: Don't fall back to -L if using --extern The compiler would previously fall back to using `-L` and normal lookup paths if a `--extern` path was specified but it did not match (wrong architecture, for example). This commit removes this behavior and forces the hand of the crate loader to always use the `--extern` path if specified, no matter whether it is correct or not. This fixes a bug today where the compiler's own libraries are favored in cross compilation by accident. For example when a crate using the crates.io version of `log` was cross compiled, Cargo would compile `log` for the target architecture. When loading the macros, however, the compiler currently favors using the host architecture (for plugins), and because the `--extern log=...` pointed at an rlib for the target architecture, that lookup failed. The crate loader then fell back on `-L` paths to find the compiler-used `log` crate (the wrong one!) and then a compile failure happened because the logging macros are slightly different. 2015-02-06 13:40:00 -08: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 16:27:57 -05:00			`# ignore-freebsd`
			`# ignore-openbsd`
fix solaris ignore 2023-03-16 14:18:07 +01:00			`# ignore-solaris`
fixing some tests and temporarily disabling others to get Bitrig build working 100% 2015-03-23 12:48:42 -07:00
rustc: Don't fall back to -L if using --extern The compiler would previously fall back to using `-L` and normal lookup paths if a `--extern` path was specified but it did not match (wrong architecture, for example). This commit removes this behavior and forces the hand of the crate loader to always use the `--extern` path if specified, no matter whether it is correct or not. This fixes a bug today where the compiler's own libraries are favored in cross compilation by accident. For example when a crate using the crates.io version of `log` was cross compiled, Cargo would compile `log` for the target architecture. When loading the macros, however, the compiler currently favors using the host architecture (for plugins), and because the `--extern log=...` pointed at an rlib for the target architecture, that lookup failed. The crate loader then fell back on `-L` paths to find the compiler-used `log` crate (the wrong one!) and then a compile failure happened because the logging macros are slightly different. 2015-02-06 13:40:00 -08:00			`HOST := $(shell $(RUSTC) -vV \| grep 'host:' \| sed 's/host: //')`
			`ifeq ($(findstring i686,$(HOST)),i686)`
			`TARGET := $(subst i686,x86_64,$(HOST))`
			`else`
			`TARGET := $(subst x86_64,i686,$(HOST))`
			`endif`

			`all:`
			`$(RUSTC) foo.rs -C extra-filename=-host`
			`$(RUSTC) bar.rs -C extra-filename=-targ --target $(TARGET)`
			`$(RUSTC) baz.rs --extern a=$(TMPDIR)/liba-targ.rlib --target $(TARGET)`