Running Pure 64-Bits On FreeBSD.

[MetalHead]

How would one go about running a pure 64 bit system on FreeBSD? None of
the ports I'm using depends on (any) x32 libraries. I notice during buildworld that x32 code is being compiled.

Btw, what kind of (optimisations) are you guys dropping
in /etc/make.conf? I've got.
CPUTYPE=athlon64
CFLAGS= -O2 -pipe
Is using -O3 out of the question when compiling ports and world?

You're probably thinking that I should leave well enough alone, nah, I like to see what I can get by with without breaking something.

TIA

[graudeejs]

Forget about cflag optimizations, they will only break things...
The only thing you can optimise is CPUTYTE

Just delete CFLAGS or any other flag entry.... This will save you troubles later

if you have nvidia card, you won't have video driver for 64bit

[chill]

Hi.
-O2 and -pipe are already enabled by default, like killasmurf said, you do not need to add seperate CFLAGS entries unless you have a specific reason to do so. -O3 is too aggressive and not supported.
I still refuse to use a 64 bit OS so I don't know anything about your other question. There are a lot of people here that do know about that though

[phoenix]

Search the forums for why you don't want to mess with CFLAGS. Unless you want to get into the nitty-gritty of what all the compiler does with each optimisation/option, and what happens to the FreeBSD source with each one, just don't do it.

As for running a 64-bit desktop, you won't have Flash, nVidia driver, and a few other things. Everything else will be available.

[BSDKaffee]

Originally Posted by MetalHead

You're probably thinking that I should leave well enough alone, nah, I like to see what I can get by with without breaking something.

Better keep a rescue disk handy then. There really isn't much to gain with higher optimization levels especially with the FreeBSD kernel and userland. Unless the system doesn't mean much to you, then be warned you can really mess up a buildworld with custom CFLAGS.

You probably don't want to use a strange set of CFLAGS as a blanket for all ports either since some can break. Many ports that can stand higher optimizations with usually give you an option to do so.

Originally Posted by MetalHead

CPUTYPE=athlon64

Should be:

CPUTYPE?=athlon64

This allows override where needed.

Originally Posted by MetalHead

CFLAGS= -O2 -pipe

The default is:

CFLAGS= -O2 -fno-strict-aliasing -pipe

You want to keep -fno-strict-aliasing in there since some ports can break without it. See /usr/share/examples/etc/make.conf for further explanation.