Chris's Wiki :: blog/linux/Lib64VersusLib32 Commentshttps://utcc.utoronto.ca/~cks/space/blog/linux/Lib64VersusLib32?atomcommentsDWiki2006-07-12T17:16:07ZRecent comments in Chris's Wiki :: blog/linux/Lib64VersusLib32.From 67.181.30.74 on /blog/linux/Lib64VersusLib32tag:CSpace:blog/linux/Lib64VersusLib32:ef90f5d2e83e06f7492466f0f82256d69115372dFrom 67.181.30.74<div class="wikitext"><p>There is no controversy, not even a small one. It's very clear that Debian made an awful mistake. It was caused by the lack of multiarch support in dpkg and general lack of direction and architecture in the distro. They have a bunch of brilliant hackers, each fortified in his little package fortress, and no good people with the overarching scope of thinking.</p>
<p>It is the same error which ia64 upstream committed, by the way. It always happens if developers think of compatibility as an add-on.</p>
<p>-- Pete</p>
</div>2006-07-12T17:16:07ZFrom 74.12.143.77 on /blog/linux/Lib64VersusLib32tag:CSpace:blog/linux/Lib64VersusLib32:f987982f2bb69b56628c3895905ba491c2e0e768From 74.12.143.77<div class="wikitext"><p>Solaris has dealt with 32/64-bit compatibility for about 10 years or longer. The 64-bit libs reside in a separate directory, e.g. /usr/lib/sparcv9, while the 32-bit libs remain in /usr/lib for compatibility. Similarly for Solaris_x86.</p>
<p>Oscar@MIE</p>
</div>2006-07-12T12:07:29Z