Compiling is still broken though (when using intended LDFLAGS). This time it was while emerging "sudo". I checked the config.log, but it was all gobbledy-gook to me; anything in particular I should be looking for?

Just logged into Gnome on my new system that went from bootstrap to desktop with these LFLAGS set.

The system was really ailing so everything is a lot faster, though I don't know how much of that speed is just from the old system being so messed up.

Just wanted people to know they were safe...___________________
If you play a Windows CD backwards you can hear demonic voices... Played forward it does something even more terrifying... It installs Windows.

Careful with the flags guys, I hope this doesn't turn into another CFLAGS debacle...

Anyways, "-z combreloc" and "-z lazy" are unneeded, since I believe they are set by default, and "--relax" isn't supported on x86 (as far as I can tell). The only flag out of the ones you have used that would actually do anything, "--enable-new-dtags", is unproven in regards to distro-wide testing like "-O1" has received with Ubuntu, so just be cautious.

Went smoothly, and i can say, my server runs really great_________________"The glue that holds all relationships together -- including the relationship between the leader and the led is trust, and trust is based on integrity."

For the LDFLAGS I actually paused (ctrl-z) the emerge-process after it finished unpacking, and edited /var/tmp/portage/qt-3.3.3-r1/work/qt-x11-free-3.3.3/mkspecs/linux-g++/qmake.conf manually. I think I added my LDFLAGS to LFLAGS_RELEASE or something like that.