Dear Andreas, dear listmembers, I found the reason for the failure - without the ability to explain. For the building process I was using a special rpmrc without the "-g" option because this is needed IMHO for building the kernel based on the suse packaging concept. This missing "-g" screwed things up for glibc. If I leave "-g" in all tests (besides the floating point issue) pass smoothly, the tst-signal1 as well. If someone has an explanation, I'd be more than happy to understand :-) By the way: upgrading is not fun. New releases come with new bugs - I cannot cope with bug hunting on my main system, I needed a compiler that works better than the one I had had before. Everything beyond that like making linux-2.6.11 compile and run with gcc 4.1.2 is work, but can be decouplded from the system operation. As long as programs get shipped without having ever been run only once (10.2: xcdroast is a mess; texmacs was a mess ...) the degree of fun with upgrades is very limited. Thanks a lot for your feedback, take care Dieter Am Freitag, 27. Juli 2007 17:49 schrieb Andreas Jaeger:
Dieter Jurzitza
writes: Dear listmembers, maybe offtopic, but maybe someone could give me a pointer where to ask / This could be a kernel bug. I would really advice to update to 10.2 instead of updating those components yourself.
-- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) ----------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org