Re: Making World For amd64
Chris Whitehouse wrote: > 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 > I guess I should have been a bit clearer about *why* I care. (BTW, all the answers were very helpful, so thanks all for that.) First, I was just generally curious about how 32- vs. 64-bit support was decided at compile time. Secondly, what got me started looking into this is when I realized I had 64-bit capable hardware in my lab, which I'd always had running 32-bit OSs. As I installed AMD64, I got to wondering just what level of compatibility existed (at the binary) level between the two, hence all my questions. Incidentally, I ran into a problem - that has nothing to do with word width AFAICT - when I installed 64-bit FreeBSD on one of the machines that historically has run 32-bit Linux (without the problem). The specific problem is that I have an MSI P4M900M2-L mobo and Pentium D on this machine that FreeBSD cannot find the APIC, so it always runs uniproc even with an SMP kern. I have to go back and check, but I am pretty sure this is not a 32-bit vs. 64-bit problem. Like I said, SUSE Linux has no problem running SMP on this same exact hardware, so it does seem to be a FreeBSD thing. Anyone else seen this kind of problem before? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
On Thu, Jun 26, 2008 at 04:29:20PM -0500, Tim Daneliuk wrote: > Erik Trulsson wrote: > > >> 1) How does make world know whether to build 32-bit or 64-bit binaries? > > > > It will build for whatever system you have installed. > > If you are running a 32-bit system it will make 32-bit binaries, and if > > you are running a 64-bit system it will make 64-bit binaries. > > > > > By "running", you mean which kernel is booted, I presume. No, I mean which variant of FreeBSD you have installed and is using. Kernel and userland. > > > > >> 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the > >> 64-bit system? > > > > Assuming the 32-bit system is 'i386' and the 64-bit system is 'amd64' then > > you are supposed to be able to do so (but I don't know how well it works in > > practice). Otherwise no. (Running a i386 binary on a sparc64 system won't > > work.) > > Right. I should have been more clear. It would be unreasonable to expect > binaries for entirely different machine architecture to run on other > kinds of machinery. My question was limited to x86 class machines. For the most part it helps if you think of amd64 and i386 as entirely different architectures - because that is essentially how FreeBSD treats them. Just about the the only thing that is special (in FreeBSD) about i386-amd64 compared to all other possible architecture pairs is that it is possible (with a few limitations) to run i386 userland binaries on an amd64 system. Apart from that you cannot mix and match i386/amd64 any more than you can with ia64/ppc. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
On Thu, Jun 26, 2008 at 04:31:37PM -0500, Tim Daneliuk wrote: > >> 1) How does make world know whether to build 32-bit or 64-bit binaries? > > > > It always uses the native format. amd64 == 64 bit, i386 == 32 bit > > Don't mean to beat this to death, but can you say just a bit more > about this please. If I am running an i386 kernel on 64-bit capable > processor, I assume I will get 32-bit binaries or not? IOW, what > triggers makeworld to do something in 32- vs. 64-bit mode? The > *kernel* currently executing or the underlying hardware capability? Normally, the currently running system. The makefile in /usr/src calls 'uname -p' to determine this. However, it is possible to do a cross-build (build kernel and world for another architecture). Google 'cross-building FreeBSD'. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpttgmE43OV0.pgp Description: PGP signature
Re: Making World For amd64
Tim Daneliuk wrote: Tim Daneliuk wrote: Kris Kennaway wrote: 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? It always uses the native format. amd64 == 64 bit, i386 == 32 bit Don't mean to beat this to death, but can you say just a bit more about this please. If I am running an i386 kernel on 64-bit capable processor, I assume I will get 32-bit binaries or not? IOW, what triggers makeworld to do something in 32- vs. 64-bit mode? The *kernel* currently executing or the underlying hardware capability? Let me be even more specific: If I install 32-bin x86 FreeBSD on, say, a Pentium D machine that is 64-bit capable, when I makeworld, will this result in 32- or 64-bit binaries? Ditto if I do makekernel. 32 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
On Thu, Jun 26, 2008 at 11:19:15PM +0200, Erik Trulsson wrote: > On Thu, Jun 26, 2008 at 03:51:40PM -0500, 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? > > It will build for whatever system you have installed. The system Makefile calls 'uname -p' to get the system's processor architecture. > If you are running a 32-bit system it will make 32-bit binaries, and if > you are running a 64-bit system it will make 64-bit binaries. By default, amd64 also builds 32-bit libraries (/usr/lib32), unless you set WITHOUT_LIB32=true in /etc/src.conf. > > 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the > > 64-bit system? > > Assuming the 32-bit system is 'i386' and the 64-bit system is 'amd64' then > you are supposed to be able to do so You will need a kernel (such as GENERIC) built with 'options COMPAT_IA32'. >(but I don't know how well it works in > practice). Otherwise no. (Running a i386 binary on a sparc64 system won't > work.) You will also need all the libraries that the application depends on in 32-bit versions. Either by copying them from a 32-bit system (built from the same source version) or by doing a cross-build. There was a thread some time ago (not sure if it was in -questions or -amd64) about using a 32-bit jail on amd64. That might be of interest. > > 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? > > If you have installed the amd64 variant of FreeBSD (for example) then > all binaries (userland and kernel alike) will have been compiled for > the amd64 architecture (and thus 64-bit.) If you are running the i386 > variant then all binaries will have been compiled for i386 (and thus > 32-bit.) You can have both 32-bit and 64-bit systems on one machine, provided you put them on separate slices/partitions. Obviously you cannot have both a 32-bit and a 64-bit version of e.g. /bin/sh on one partition. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpKkivgACSnl.pgp Description: PGP signature
Re: Making World For amd64
Tim Daneliuk wrote: Kris Kennaway wrote: 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? It always uses the native format. amd64 == 64 bit, i386 == 32 bit Don't mean to beat this to death, but can you say just a bit more about this please. If I am running an i386 kernel on 64-bit capable processor, I assume I will get 32-bit binaries or not? IOW, what triggers makeworld to do something in 32- vs. 64-bit mode? The *kernel* currently executing or the underlying hardware capability? I'm pretty sure this is all documented ;) The "i386" version of FreeBSD is 32-bit. You can run it on any i386-compatible machine, including amd64/em64t machines. The "amd64" version of FreeBSD is 64-bit. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
Tim Daneliuk wrote: > Kris Kennaway wrote: >> 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? >> It always uses the native format. amd64 == 64 bit, i386 == 32 bit > > Don't mean to beat this to death, but can you say just a bit more > about this please. If I am running an i386 kernel on 64-bit capable > processor, I assume I will get 32-bit binaries or not? IOW, what > triggers makeworld to do something in 32- vs. 64-bit mode? The > *kernel* currently executing or the underlying hardware capability? > > Let me be even more specific: If I install 32-bin x86 FreeBSD on, say, a Pentium D machine that is 64-bit capable, when I makeworld, will this result in 32- or 64-bit binaries? Ditto if I do makekernel. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
Kris Kennaway wrote: > 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? > > It always uses the native format. amd64 == 64 bit, i386 == 32 bit Don't mean to beat this to death, but can you say just a bit more about this please. If I am running an i386 kernel on 64-bit capable processor, I assume I will get 32-bit binaries or not? IOW, what triggers makeworld to do something in 32- vs. 64-bit mode? The *kernel* currently executing or the underlying hardware capability? TIA, Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
Erik Trulsson wrote: >> 1) How does make world know whether to build 32-bit or 64-bit binaries? > > It will build for whatever system you have installed. > If you are running a 32-bit system it will make 32-bit binaries, and if > you are running a 64-bit system it will make 64-bit binaries. > By "running", you mean which kernel is booted, I presume. > >> 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the >> 64-bit system? > > Assuming the 32-bit system is 'i386' and the 64-bit system is 'amd64' then > you are supposed to be able to do so (but I don't know how well it works in > practice). Otherwise no. (Running a i386 binary on a sparc64 system won't > work.) Right. I should have been more clear. It would be unreasonable to expect binaries for entirely different machine architecture to run on other kinds of machinery. My question was limited to x86 class machines. -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
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? It always uses the native format. amd64 == 64 bit, i386 == 32 bit 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the 64-bit system? Yes, amd64 also builds 32-bit libraries to support this. 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? You can't run 64 bit binaries on a 32-bit kernel, but you can the other way around. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
On Thu, Jun 26, 2008 at 03:51:40PM -0500, 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? It will build for whatever system you have installed. If you are running a 32-bit system it will make 32-bit binaries, and if you are running a 64-bit system it will make 64-bit binaries. > > 2) Can a binary from a 32-bit FreeBSD system be run unmodified on the > 64-bit system? Assuming the 32-bit system is 'i386' and the 64-bit system is 'amd64' then you are supposed to be able to do so (but I don't know how well it works in practice). Otherwise no. (Running a i386 binary on a sparc64 system won't work.) > > 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? If you have installed the amd64 variant of FreeBSD (for example) then all binaries (userland and kernel alike) will have been compiled for the amd64 architecture (and thus 64-bit.) If you are running the i386 variant then all binaries will have been compiled for i386 (and thus 32-bit.) -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
Sean Cavanaugh wrote: > > > -- > From: "Tim Daneliuk" <[EMAIL PROTECTED]> > Sent: Thursday, June 26, 2008 4:51 PM > To: "Kris Kennaway" <[EMAIL PROTECTED]>; "FreeBSD Mailing List" > > Subject: Re: Making World For amd64 > >> 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, > > > I take this to mean you have an i386 install and want to compile amd64 > on it. No - although that is an interesting question in its own right. I was more interested in the general question of whether 32-bit and 64-bit binaries are the same or different. I would assume that something has to be compiled to take advantage of 64-bit operations. But this then leads to the two questions: How does makeworld know which way to build the binaries and Can a 32bit binary be run on a 64bit system (or vice versa) in some compatibility or degraded mode... -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
-- From: "Tim Daneliuk" <[EMAIL PROTECTED]> Sent: Thursday, June 26, 2008 4:51 PM To: "Kris Kennaway" <[EMAIL PROTECTED]>; "FreeBSD Mailing List" Subject: Re: Making World For amd64 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, I take this to mean you have an i386 install and want to compile amd64 on it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
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, -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
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? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making World For amd64
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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Making World For amd64
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? -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
