>Great, thanks again for being extraordinarily helpful. Why do you
>think I keep asking questions? because I like being told something is
You have been asking questions about this stuff that seem to ignore the fact
that we don't support n32.
>I want to get this thing working, and I am more than happy to
>help out the effort. If no one will tell me what the problem is, then
>I'm going to have a hard time fixing it. here, ready?
The problem is that none of us have answers for your questions, therefore we
*can't* tell you what the problem is. Generally, n32 is so broken that the
developer team can't even use it. The multithreaded bug is a horribly painful
one that only somebody with good kernel hacking skills can fix, for example.
Any other bugs you may hit are just extra broken stuff that add to n32's
unusability. Add to that the fact some senior mips kernel and glibc
developers have told me that our toolchain and glibc are old enough
(relatively speaking) that they are surprised n32 works at all for us. There
isn't much we can do about this until newer versions are pushed forward in
>I hereby claim
>myself as a developer, now will you stop belittling me? I may not know
>all that much about the problems here, but I've got time and energy
>and I can easily put it someplace else.
Fix the n32 multithreaded kernel bug and we'll talk (see
http://beerandrocks.net:8080/~spbecker/oops/). Until then, you are just
complaining about problems we can't help you with. Furthermore, you started
this thread with complaining about your shmem problem, and only additional
questioning from Redhatter revealed that it was a n32 specific problem (as so
many are when you are playing with unsupported stuff like this). From now on,
you need to specify what sort of userland, as well as what kernel version(s)
you reproduced it with before we can even begin to help you.
firstname.lastname@example.org mailing list