Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • I did so and while it got rid of the error, I got a new one about gnu/stubs-32.h which is in libc6-dev. I'm just going to go back to a 64 bit 12.04. Thanks! Accepting because it did get rid of the error. Commented Sep 29, 2012 at 17:25
  • 2
    Hmm, so you already tried doing what this suggests? stackoverflow.com/questions/7412548/… Commented Sep 29, 2012 at 22:56
  • 1
    how is 64-bit related to multiprocessing (core use) ? Commented Jan 28, 2013 at 11:28
  • 1
    The main change from 32-bit to 64-bit is how much memory the system can use, not multiprocessing. 32-bit systems support ~2GB of memory, whereas 64-bit systems can support up to 16 exabytes (though technically 64-bit Intel and AMD machines only address 48-bits for a max of 256 TB, which is still good enough... for now). Commented Jul 5, 2013 at 18:28
  • 2
    @DanAlbert: 32-bit systems support a VM model based on the PAGE_OFFSET macro value defined within the kernel (only configurable at kernel build time (usually via CONFIG_VM_SPLIT)). A typical default for 32-bit systems on Linux is a "3:1" VM split, implying 3GB usermode virtual memory and 1GB kernelmode VM. It could be 2:2, could be 1:3. Commented Mar 24, 2014 at 11:41