On Wednesday 08 April 2009 05:04:25 Mike Frysinger wrote: > On Wednesday 08 April 2009 04:14:05 ipif wrote: > > I'm working on an embedded sparc system with linux-2.6.21 and > > uclibc-0.9.30. When I try to touch a fifo, touch itself stops waiting for > > data. This is not the expected behavior, as it should just exit. > > you first have to prove that this is a bug in uClibc and not touch. where > exactly are you getting touch from ? did you try running gdb against that > to see if it is the one doing the read and not uClibc ? considering the > functions (most likely) involved, i doubt uClibc is the culprit. > > > On my pc (glibc) the last part looks like this: > > what glibc is doing is largely irrelevant as the version of touch built > there will use wildly different interfaces (the *at funcs in this case).
anyone who happens to also hit this, it did turn out to be an issue with coreutils' touch (well, the gnulib utimes module when cross-compiling) and not uClibc. see this thread for info: http://lists.gnu.org/archive/html/bug-coreutils/2009-04/msg00090.html -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ uClibc mailing list uClibc@uclibc.org http://lists.busybox.net/mailman/listinfo/uclibc
