Date: Thu, 26 Jun 2008 23:14:13 +0100 From: Chris Whitehouse <cwhiteh@onetel.com> To: Tim Daneliuk <tundra@tundraware.com> Cc: FreeBSD Mailing List <freebsd-questions@FreeBSD.org> Subject: Re: Making World For amd64 Message-ID: <486414B5.6020608@onetel.com> In-Reply-To: <4864015C.7010805@tundraware.com> References: <4863F317.6010701@tundraware.com> <4863F4A7.1070909@FreeBSD.org> <4863F5A3.6050209@tundraware.com> <4863FC2A.5040909@FreeBSD.org> <4864015C.7010805@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Daneliuk wrote: > Kris Kennaway wrote: >> Tim Daneliuk wrote: >>> Kris Kennaway wrote: >>>> Tim Daneliuk wrote: >>>>> Is there anything special one has to do when doing a make world >>>>> intended for 64-bit FreeBSD or is it sufficient to build the 64-bit >>>>> kernel and make world as everywhere else? >>>> The same as everywhere else. >>>> >>>> Kris >>> So, I take it that this means that all the userspace programs, ports, >>> packages, utilities, etc. do *not* take advantage of the 64-bit >>> extensions. That is, only the kernel gets the benefit of the >>> wider word. Is that correct? >>> >> No, everything is 100% native. >> >> Kris >> > > OK, these may be really stupid questions but: > > 1) How does make world know whether to build 32-bit or 64-bit binaries? > > 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the > 64-bit system? > > 3) If I reboot with 32-bit or 64-bit kernels, does the system magically > somehow make the userland stuff work natively at the word width? > If so, how? > > TIA, > This might be a really stupid answer :p and maybe I have misunderstood the context of your question but when you initially downloaded an ISO to install you already chose whether it is 32 or 64 bit. Everything else, like which source and ports you get when you upgrade, follows from that (barring fancy stuff like cross compiling etc) Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?486414B5.6020608>