diff options
authorAvatar Bo ├śrsted Andresen <zlin@exherbo.org> 2016-12-19 17:22:02 +0100
committerAvatar Bo ├śrsted Andresen <zlin@exherbo.org> 2016-12-19 17:22:02 +0100
commitcb2fb1640197d7e1626c9def9fbb85454a21832f (patch)
parent005b7deaa94aab7f69d4b1b622481021fda8f6c7 (diff)
Update fix-linkage TODO.
Change-Id: Ie994596b3aacdf98420e30dff732d0bd09df0f16
1 files changed, 8 insertions, 5 deletions
diff --git a/multiarch-TODO.mkd b/multiarch-TODO.mkd
index 95e227c..589d4a5 100644
--- a/multiarch-TODO.mkd
+++ b/multiarch-TODO.mkd
@@ -90,13 +90,16 @@ doesn't complain about that.
zlin | my reasoning too
ciaranm | in which case we have another reason cross isn't ready to merge
-### considering wrong installed package for fix-linkage
+### fix-linkage -- -mx or fix-linkage -- -4 i686-pc-linux-gnu behaves funny
-If a package is installed on host and on cross with broken linkage for the
-cross version, but correct linkage for the host version, then cave fix-linkage
-will keep reinstalling the host version of that package.
+cave fix-linkage -- -4 i686-pc-linux-gnu checks what's broken on cross and then
+reinstalls the default version. This should just ignore -4 because there's no
+-mx and thus check what's broken on default and reinstall that.
-Should only check the ones in the selected destination for the package.
+cave fix-linkage -- -mx checks what's broken on default and then builds it on
+cross. this requires there being only one cross target to pick from in order to
+reproduce the problem. therefore it should check what's broken on that target
+and rebuild that.
### Per target options