There are some ports that they can be build only for i386, or you will see on flags that some options are only for i386. But all this is a very small part on ports. But general you will have no problem. Me too amd64 arch I use for my desktop and everything is running wellI have a system with an amd64 processor. Does the amd64 FreeBSD version support all 32-bit apps without issue?
Not sure but if the answer on this question is yes, then we solve the "problem" of the first questionCan a binary built on i386 run on amd64?
The only reason that I see to stay on i386, is if you run a specific program that runs only on i386, the answer on the second question is no and you can not work with alternative tool except this. For all the othes, go to amd64In other words, is there any reason to stick with i386 in this case?
grep -R ONLY_FOR_ARCHS /usr/ports/*
Yes, this should be just fine either wayqsecofr said:I'd like to add a question: if the NFS server is i386, can the NFS client be amd64? (or vice-versa even)
As long as you have COMPAT_FREEBSD32 defined in your kernel config, i386 FreeBSD binaries should work. Note that this option name is somewhat confusing, since all of the other COMPAT_FREEBSD* options are for compatibility with different FreeBSD releases, not architectures.Pushrod said:I have a system with an amd64 processor. Does the amd64 FreeBSD version support all 32-bit apps without issue? Can a binary built on i386 run on amd64?
-m32 -DCOMPAT_32BIT -L/usr/lib32 -B/usr/lib32
Pushrod said:Any disadvantages? Does memory use change much on amd64? In Win64, memory usage is significantly higher than with Win32.