rust/tests/run-make-fulldeps/suspicious-library/Makefile

include ../tools.mk

all:
	$(RUSTC) foo.rs -C prefer-dynamic
	touch $(call DYLIB,foo-something-special)
	touch $(call DYLIB,foo-something-special2)
	$(RUSTC) bar.rs
Diagnose missing includes in run-make tests 2022-08-22 19:00:00 -05:00			`include ../tools.mk`
rustc: Prevent false positives in crate loading Previously, any library of the pattern `lib<name>-<hash>-<version>.so` was >considered a candidate (rightly so) for loading a crate. Sets are generated for each unique `<hash>`, and then from these sets a candidate is selected. If a set contained more than one element, then it immediately generated an error saying that multiple copies of the same dylib were found. This is incorrect because each candidate needs to be validated to actually contain a rust library (valid metadata). This commit alters the logic to filter each set of candidates for a hash to only libraries which are actually rust libraries. This means that if multiple false positives are found with the right name pattern, they're all ignored. Closes #13010 2014-03-19 10:47:59 -05:00
			`all:`
rustc: Default to static linking dylibs If a dylib is being produced, the compiler will now first check to see if it can be created entirely statically before falling back to dynamic dependencies. This behavior can be overridden with `-C prefer-dynamic`. Due to the alteration in behavior, this is a breaking change. Any previous users relying on dylibs implicitly maximizing dynamic dependencies should start passing `-C prefer-dynamic` to compilations. Closes #18499 [breaking-change] 2014-11-03 01:02:53 -06:00			`$(RUSTC) foo.rs -C prefer-dynamic`
rustc: Prevent false positives in crate loading Previously, any library of the pattern `lib<name>-<hash>-<version>.so` was >considered a candidate (rightly so) for loading a crate. Sets are generated for each unique `<hash>`, and then from these sets a candidate is selected. If a set contained more than one element, then it immediately generated an error saying that multiple copies of the same dylib were found. This is incorrect because each candidate needs to be validated to actually contain a rust library (valid metadata). This commit alters the logic to filter each set of candidates for a hash to only libraries which are actually rust libraries. This means that if multiple false positives are found with the right name pattern, they're all ignored. Closes #13010 2014-03-19 10:47:59 -05:00			`touch $(call DYLIB,foo-something-special)`
			`touch $(call DYLIB,foo-something-special2)`
			`$(RUSTC) bar.rs`