rust/tests/run-make/invalid-so/Makefile

include ../tools.mk

DYLIB_NAME := $(shell echo | $(RUSTC) --crate-name foo --crate-type dylib --print file-names -)

all:
	echo >> $(TMPDIR)/$(DYLIB_NAME)
	$(RUSTC) --crate-type lib --extern foo=$(TMPDIR)/$(DYLIB_NAME) bar.rs 2>&1 | $(CGREP) 'invalid metadata files for crate `foo`'
move `tools.mk` to run-make apparently I missed some tests in the last commit. Rather than having dozens of tests use the long version, use the short version in `run-make` and the long version in `run-make-fulldeps` (which is now only three tests) 2023-03-30 12:58:50 +00:00			`include ../tools.mk`
Improve error when an .rlib can't be parsed This usually describes either an error in the compiler itself or some sort of IO error. Either way, we should report it to the user rather than just saying "crate not found". This only gives an error if the crate couldn't be loaded at all - if the compiler finds another .rlib or .rmeta file which was valid, it will continue to compile the crate. Example output: ``` error[E0785]: found invalid metadata files for crate `foo` --> bar.rs:3:24 \| 3 \| println!("{}", foo::FOO_11_49[0]); \| ^^^ \| = warning: failed to parse rlib '/home/joshua/test-rustdoc/libfoo.rlib': Invalid archive extended name offset ``` 2021-08-26 18:37:44 +00:00
			`DYLIB_NAME := $(shell echo \| $(RUSTC) --crate-name foo --crate-type dylib --print file-names -)`

			`all:`
			`echo >> $(TMPDIR)/$(DYLIB_NAME)`
			$(RUSTC) --crate-type lib --extern foo=$(TMPDIR)/$(DYLIB_NAME) bar.rs 2>&1 \| $(CGREP) 'invalid metadata files for crate `foo`'