Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
elfdeps: Add full multiarch deps support #360
Conversation
|
Why isn't this "can be enabled with --multiarch" and no-multiarch is the default? |
|
addArchedDep seems to be identical to addDep, so I don't see why you don't just use ei->marker but generate it differently. |
|
@mlschroe I originally had it with As for why I didn't touch |
|
@mlschroe Oh wait, I see what you're talking about. You mean use |
|
@mlschroe I removed the redundant |
Conan-Kudo commentedNov 15, 2017
•
Edited 5 times
-
Conan-Kudo
Nov 15, 2017
-
Conan-Kudo
Nov 15, 2017
-
Conan-Kudo
Nov 15, 2017
-
Conan-Kudo
Nov 15, 2017
-
Conan-Kudo
Nov 15, 2017
This changes elfdeps to emit dependency strings that contain full architecture names instead of just declaring whether something is "64bit". This means that systems that allow more than two architectures to be installed on the same computer will actually be able to resolve library dependencies correctly.
This means that RPM dependencies would be compatible with system library install schemes like Debian's, where libraries are installed into subdirectories under
/usr/libthat are named after the platform triple. It also allows for multiarch installations where foreign architecture packages are automatically relocated to be installed under a system root target location (e.g./usr/<triple>/lib(64)) as is done in distributions like Exherbo.This behavior can be enabled by passing
--multiarch-depsor by setting%__multiarch_depsto1in the spec or vendor configuration.