Sorry for dig it out again :-( If we put o32 multilib libraries in to /usr/lib directly, it will make lots of packages ftbfs, if they use -L/usr/lib.
For this problem, we have another option that is: put ld.so.1 for o32 still in /lib while put other libraries to /usr/libo32 and /libo32. With a build option, ld.so.1 still can find libraries in both /usr/libo32 and /usr/lib/. Will this acceptable? -- To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cakcpw6vj7gpom_ua9gi-k2-tu4y0hz-5j8omgkfmeruvny9...@mail.gmail.com
