I am running the latest hardened toolchain from hardened-development overlay, keyworded ~amd64, no-multilib, hardened-sources system with grsecurity (and pax) enabled in the kernel. Now here's my issue:

With uvesafb:off appended to the kernel line, everything boots and runs fine.
With uvesafb ...

Does this still work for someone? Just tried to install 5.1.41 but the emerge process bumps out while patching.
The overlay was just updated with what appears to be 5.1.41-r1 which compiles successfully for me.

So step up and help maintain mysql in portage.
I would consider doing this, however ...

No. I have -r2 installed, but it wants to downgrade to 5.1.41 and fails on patching. -r2 has been removed from the repo and I'm not sure why. Does anybody know how to contact this overlay maintainer?

I didn't even notice that in my upgrade to -r2. It appears to still compile and run fine. I'd imagine it would need to be reported to the overlay maintainer, whose contact info I don't know.

Read through this bug and you will get an idea of the primary maintainer's position on MySQL builds:
http://bugs.gentoo.org/194561

Apparently, they don't pass the quality checks/testing done. However, I disagree in that these versions shouldn't even be added to the tree. They should, and ones that ...

KDE4 is a pain when you don't realize tools like autounmask are available. You unmask one package, just to follow with another dependency. 50 unmasked packages and an hour later you get a clean emerge.
There is no need for that. Just follow the KDE4 guide and grab the package.keywords file that is ...

I believe the executable is firefox vs firefox-bin. Running the -bin will run the binary version. I am not sure if you can run them at the same time, as firefox checks to see if there are firefox processes already running, but you are more than welcome to try.

I don't think I can be of much more assistance here. My only x64 build is an Intel VM (and gui-less), my other box is x86 (which FF 3.0.6 runs fine on). How about masking =www-client/mozilla-firefox-3.0.6, which will pull in 3.0.5 instead? No reason to go all the way back to 2.x series.

Also, you ...

Sorry about that, I forgot about that little caveat. I still do not think it is an issue with glibc though, since the troubled patches should have been removed in -r2. Did you look into plugins that may be causing this? Also, does Firefox start ever? Or is it just intermittent. The bug you were ...

You know, if you don't want it, you can just # emerge -C busybox and move on. Hell, even mask it if you don't want it to pop back up again. I agree with the aforementioned views of having it as a recovery tool and default part of the system set. For most users, this is acceptable. However, you are ...

Looks like that may be a diff issue, since the problem patch was dropped in the -r2 version of glibc, that and the issue was resolved with the release of 3.0.6. I suppose you could try emerging glibc-2.9_p20081201 before any of the recent patches were added. Also, I would look into the flash plugin ...

ahnkle wrote:/usr/lib64/qt4/libQtSvg.so: undefined reference to `QCss::Parser::parse(QCss::StyleSheet*)'

Based on the above line, I'd venture to guess x11-libs/qt-svg would the package to recompile. Two things you should probably do as well:

Did you recompile it a second time (to ensure it wasn't a compile time error/issue)? If so, did you try compiling it without any USE flags (# USE="-*" emerge -av mozilla-firefox)? That should isolate USE issues, which are variable.

Try launching it from a terminal and posting any output generated ...

KDE4 is a pain when you don't realize tools like autounmask are available. You unmask one package, just to follow with another dependency. 50 unmasked packages and an hour later you get a clean emerge. Now if I'm not mistaken KDE4.2 is not masked, it is just marked as unstable (ie. use package ...

To keep your box busy. Seriously, do you want a lazy box? Especially a "pretty" secure one?

<Seriousness>
Busybox is a toolkit. Its used on a lot of platforms. Even my DD-WRT router has a version of it, and I'd like to consider it "pretty" secure. Claiming busybox is a security issue is similar to ...

You might look into GIT if you are going to be importing changes from your outsourced developer group into your own (combining them). I think that GIT would provide a better architecture since this essentially the same setup the kernel development (Linus and friends) uses, where you can pick and ...

Is /samba/packages a network mount? Your user/group ownership looks wrong. I would expect the files and directories to be owned by root.
I'd assume from the /samba it is. The real issue is that we see chown issues (or any write/modify actions) failing. I don't think the file perms here are the ...

The green asterisk from gcc-config -l means that is the compiler the system is currently set to use. With it being next to 4.3.3, it *should* mean 4.3.3 is what it is set to use.

env-update && source /etc/profile didn't help? You can try doing a gcc-config # (where the # equals the number next to ...

sera wrote:sandbox-1.3.9 is now in portage and should contain a working fix.

This issue does indeed appear to have been fixed in sandbox-1.3.9. Compiles have no errors with it installed.

dev ~ # emerge -s coreutils
Searching...
[ Results for search key : coreutils ]
[ Applications found : 2 ]

* sys-apps/coreutils
Latest version available: 7.1
Latest version installed: 7.1
Size of files: 9,316 kB
Homepage: http://www.gnu.org/software/coreutils/
Description: Standard GNU file ...

Yep. Everything works fine with sandbox-1.3.7, but any package depending on libtool fails to emerge with sandbox-1.3.8 installed, no matter what I recompile when 1.3.7 is installed.

Zorry, your suggestion did not work. Whenever sandbox-1.3.8 is installed, emerges depending on libtool fail.

sera wrote:Well you mean the other way around, right?

Yes, my apologies for that. I have corrected the post. I will try Zorry's above recommendation today as well.

emerge -e system before re-upgrading to sandbox-1.3.8 did not fix the issue. so for now, i am sticking with 1.3.7.

Well, downgrading to sandbox-1.3.7 seemed to fix the issue. I am in the process of updating world, and then I'll try emerge -e system, update to sandbox-1.3.8, and see if recompile still work.