Bug#324795: libc6 in stable broken on arm4vl
At Sun, 11 Sep 2005 01:05:42 -0400,
Rob Warren wrote:
> I've just installed sarge onto the second netwinder without any
> problems with libc 2.3.2.ds1-22 with the netboot image, kernel 2.4.27.
>
> ...then I tried to boot from the kernel I was previously using (2.2.19)
> and got the dreaded result:
> "unsupported llseek call standard"
What was this message come from? Dmesg?
> Tried with 2.2.17 and got the same result.
>
> Can we add a dependency to the libc package to prevent this from
> happening to others?
Before doing any work, I would like to clear what your problem was.
Previously we discussed as follows:
> > libc6 from 2.2.5-11.8 to 2.3.2.ds1-22 with a message along the lines of
> > 'can't seek in file xxxxxx'. dmesg would report 'Bad number of
> > arguments for llseek()' (paraphrasing) every so often. It was
> > impossible to reserve the package install.
>
> Weird. Grep told me that dmesg (kernel 2.2.19) and glibc should not
> warn such kind of messages.
This means we need to confirm that your kernel is special or debian
standard one. If you use your custom kernel, we may not reappear such
kind of problem again.
Could you describe the following stuff? (1) your exact kernel version
and how to get it (2) the exact warning/error message.
Regards,
-- gotom
Reply to: