Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
wiki:talk:slackware:multilib [2010/07/26 22:32] – 91.78.186.240 | wiki:talk:slackware:multilib [2012/03/18 13:13] – ViyPWXaXGveapxTRg 91.224.161.250 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Discussion area for Slackware64 multilib support ====== | + | That is a difficult qtiuseon. The best answer |
- | + | ||
- | Feel free to leave comments, suggestions and constructive feedback about using multilib on Slackware64. | + | |
- | + | ||
- | --- //Eric Hameleers, Fri Aug 14 15:10:17 UTC 2009// | + | |
- | + | ||
- | ---------------------------------------------------- | + | |
- | + | ||
- | I made a Multilib Slackware following your instructions (Slackware64-current on a Lenovo Thinkpad T61) and it works -- indeed ;-) | + | |
- | + | ||
- | Now I'm able to use Skype and Adobe Reader. | + | |
- | + | ||
- | Many thanks, keep up the good work | + | |
- | + | ||
- | --- //Didier Spaier, Paris, le 26 août 2009 à 22h58// | + | |
- | + | ||
- | --------------------------------------------------- | + | |
- | + | ||
- | > Two questions: | + | |
- | > | + | |
- | > 1. Why multilib gcc/glibc are not default, or at least put in " | + | |
- | + | ||
- | Pat Volkerding decided that the first release of Slackware64 should be pure 64bit. There was a small change to the specs file in gcc and our binutils are essentially multilib, but out of the box there is no support at all for 32bit applications (running nor compiling them).\\ | + | |
- | When I started working on the 64bit port, I discussed with Pat (and the rest of the team too btw) about the possible architecture options for this new port. There were a few paths I could follow; first the pure 64bit approach using lib instead of lib64 directories (Bluewhite64 does this) or doing full multilib (like Slamd64 does). Pat was opposed to a multilib approach (not too strange, considering that at that point there was the risk that nobody would want a 32bit Slackware once the multilib Slackware64 was released), but I was opposed | + | |
- | + | ||
- | Perhaps the next release of Slackware64 | + | |
- | + | ||
- | > 2. Does the method you described works for installing and then using GRUB to boot Slackware64 system? | + | |
- | > | + | |
- | > --- //A.// | + | |
- | + | ||
- | Sure, you can build and install grub now. But... you do not need multilib Slackware64 | + | |
- | + | ||
- | + | ||
- | --------------------------------------------------- | + | |
- | + | ||
- | Thanks | + | |
- | + | ||
- | + | ||
- | --------------------------------------------------- | + | |
- | + | ||
- | > Excellent and well written guide, thank you very much! My only suggestion is to put a note somewhere that after setting up | + | |
- | > multilib, it may be necessary to reinstall NVIDIA drivers, otherwise things like wine tend to crash. | + | |
- | > --- // Andy, Mon Sep 7 14:11 UTC 2009 // | + | |
- | + | ||
- | Thanks | + | |
- | + | ||
- | --------------------------------------------------- | + | |
- | + | ||
- | Thanks | + | |
- | + | ||
- | --- //Frank van der Loo, Tue Feb 2 13:24:43 UTC 2010// | + | |
- | + | ||
- | --------------------------------------------------- | + | |
- | + | ||
- | Thanks for great job. | + | |
- | + | ||
- | I tried to compile transmission torrent client for i486 and met with trouble: | + | |
- | / | + | |
- | >156-/* The size of `long', | + | |
- | > | + | |
- | Therefore some headers are not arch independent. It was bad surprise for me.) | + | |
- | As temporary solution I had installed a curl-7.19.6-i486-1.txz package from slackware32-13.0 and compiled transmission successfully. | + | |
- | + | ||
- | --- //Magras, Mon Jul 26 22:31:43 UTC 2010// | + |