This one time, at band camp, Adrian Phillips said:
> >>>>> "Stephen" == Stephen Gran <[EMAIL PROTECTED]> writes:
> 
>     Stephen> My guess (ill informed and wildly speculative as it is)
>     Stephen> is that the linker is making a wrong guess about what
>     Stephen> thread implementation is supported by the uml kernel.  I
>     Stephen> am not sure how to diagnose that, or what to do about it.
> 
>     Stephen> All of my wild guesses make me feel like it's not a bug
>     Stephen> in clam per se, but I cannot prove it, so I leave that
>     Stephen> part up to you.
> 
> No, seeing as it affects mysql as well it would seem to indicate a
> libc error more than anything else. I was mainly interested in getting
> this in the bug DB so it would spread to google this giving others
> with the same problem a solution to work around it when they upgrade
> from woody to sarge (the person who reported the mysqld crashing, at
> bytemark.co.uk, has everything working with woody).
> 
> I'm wondering whether I should report this as a libc bug instead.

I am fairly sure it is either a libc or kernel bug, but I am not sure
which.  You will certainly get more help out of the libc people than you
will from me, though :)

If you like, just reassign this bug to lib c, or close this and open a
new one.

The relevant bts commands would be 
reassign <bug#> <package>
or
close <bug#>

end the command set with 
thanks

and include [EMAIL PROTECTED] in the list of recipients.  See the
documentation linked from bugs.debian.org for details.  Alternately, you
can just ask me to do it for you :)

Take care, and good luck with it,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        [EMAIL PROTECTED] |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

Attachment: pgpgbk1pFCyqh.pgp
Description: PGP signature

Reply via email to