Unfortunately you'll have to rebuild your install with an amd64 livecd/stage3 tarball, afaik there's no way to go from x86->amd64 while booted from your x86 enviroment as the CPU is running in x86 legacy mode and doesn't have the sense to switch to x86_64 native mode while in such an enviroment, I could be wrong however, I just wouldn't waste my time trying. Although since the Core2Duo is quicker than shit off a shovel it's no bother to rebuild an amd64 desktop inside a handful of hours.

_________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king

# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-Os -march=pentiumpro -pipe"
CHOST="i686-pc-linux-gnu"

ok you get burnt not fired_________________The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king

# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j2"

unless you want to debug your applications it is pointless to have the pointers, unless you are using something like gdm to analize the memory of a running application, you dont need them._________________My Systems - "I suggest the whole thing be coded in whitespace. Henceforth the code will be obscure and functional at the same time."

unless you want to debug your applications it is pointless to have the pointers, unless you are using something like gdm to analize the memory of a running application, you dont need them.

and that is why i have splitdebug in FEATURES and i have gdb in USE_________________when you're sitting back, in your rose pink Cadillac
Making bets on Kentucky Derby Day
I'll be in my basement room, with a needle and a spoon
And another girl to take my pain away...

unless you want to debug your applications it is pointless to have the pointers, unless you are using something like gdm to analize the memory of a running application, you dont need them.

and that is why i have splitdebug in FEATURES and i have gdb in USE

Still need the frame pointer to 'walk' the stack properly. But you have -ggdb, so gcc probably silently ignores -fomit-frame-pointer.

gcc doesnt look at USE flags iirc, it is just a system to add/remove options when compiling programs in the ebuilds._________________My Systems - "I suggest the whole thing be coded in whitespace. Henceforth the code will be obscure and functional at the same time."