Advertisement
Guest User

Untitled

a guest
May 25th, 2015
215
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.05 KB | None | 0 0
  1. 015-03-28-true-multilib
  2. Title True multilib support on amd64
  3. Author Michał Górny <mgorny@gentoo.org>
  4. Posted 2015-03-28
  5. Revision 1
  6.  
  7. Starting on 2015-03-29, we are enabling true multilib support on amd64
  8. and masking the old emul-linux-x86 package sets for removal. This
  9. change provides our users with the opportunity to build 32-bit libraries
  10. from source with all the flexibility given by ebuilds and the security
  11. of using mainline ebuilds, rather than relying on pre-packaged binary
  12. versions of them.
  13.  
  14. The switch to the new system is likely to require a specific action from
  15. the users of our multilib profiles. Since the new system collides with
  16. the old one, the Package Manager must be able to clearly satisfy all
  17. the dependencies using the new system in order to proceed. This may
  18. require unmerging packages installed from third-party repositories that
  19. have not been updated to support the new system.
  20.  
  21. In order to enable building necessary 32-bit libraries, users will be
  22. required to enable the abi_x86_32 USE flag on respective packages.
  23. This can be done using /etc/portage/package.use entries alike
  24. the following:
  25.  
  26. sys-libs/zlib abi_x86_32
  27.  
  28. In most of the cases, Portage will be able to deliver correct
  29. suggestions for that when using the --autounmask feature. However, some
  30. users may prefer setting ABI_X86 globally to enable 32-bit libraries
  31. in all packages that support building them. This can be done using
  32. the following package.use entry:
  33.  
  34. */* abi_x86_32
  35.  
  36. In case of issues, blockers especially, users are recommended
  37. to manually uninstall any emul-linux-x86 packages that may have been
  38. installed on their systems. This will aid the Package Manager
  39. in choosing the correct dependency resolution path. If using Portage,
  40. this can be done using the following command:
  41.  
  42. $ emerge -C 'app-emulation/emul-linux-x86*'
  43.  
  44. Note: 32-bit applications may be temporarily broken after this step.
  45. Therefore, it should be followed by a @world upgrade immediately.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement