FS#46786 - [lib32-mesa] [lib32-libdrm] [lib32-cairo] Cyclical dependency
Attached to Project:
Arch Linux
Opened by Que Quotion (quequotion) - Monday, 19 October 2015, 03:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 19 October 2015, 05:34 GMT
Opened by Que Quotion (quequotion) - Monday, 19 October 2015, 03:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 19 October 2015, 05:34 GMT
|
Details
Description:
First, building lib32-mesa depends* on lib32-libdrm, but lib32-libdrm failed to build because it depends on lib32-cairo: /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/../../../libcairo.so when searching for -lcairo /usr/bin/ld: skipping incompatible /usr/lib/libcairo.so when searching for -lcairo /usr/bin/ld: cannot find -lcairo collect2: error: ld returned 1 exit status So I added the dependency to lib32-libdrm's pkgbuild, and went about building lib32-cairo, which failed because it depends on lib32-mesa, which depends on lib32-libdrm. For now I can work around this by installing a binary package for lib32-libdrm. *It also depends on non-existent lib32-wayland and lib32-systemd; I made my own package for lib32-wayland (although it could be disabled) and removed lib32-systemd from the PKGBUILD (what part of systemd could mesa depend on?). Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Attempt to build any of these packages from ABS. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 19 October 2015, 05:34 GMT
Reason for closing: Not a bug
Additional comments about closing: Don't build on a dirty system.
Monday, 19 October 2015, 05:34 GMT
Reason for closing: Not a bug
Additional comments about closing: Don't build on a dirty system.
Can reporters please be granted the right to fix that (change the "Category")?
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/../../../libXvMC.so when searching for -lXvMC
/usr/bin/ld: skipping incompatible /usr/lib/libXvMC.so when searching for -lXvMC
/usr/bin/ld: cannot find -lXvMC
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/../../../libXv.so when searching for -lXv
/usr/bin/ld: skipping incompatible /usr/lib/libXv.so when searching for -lXv
/usr/bin/ld: cannot find -lXv
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-unknown-linux-gnu/5.2.0/../../../libXvMCW.so when searching for -lXvMCW
/usr/bin/ld: skipping incompatible /usr/lib/libXvMCW.so when searching for -lXvMCW
/usr/bin/ld: cannot find -lXvMCW
collect2: error: ld returned 1 exit status
(lib32-libxvmc pulls in the additional lib32-libxv dependency)
As for not having a "Packages: Multilib", that's because you keep filing them under the Arch Linux project instead of the Community Packages project.
You seem to have trouble grasping concepts. I think I'm just going to start closing most of your reports.