Paul Eggert <[EMAIL PROTECTED]> wrote: > The readlink-fp-loop test has some dependencies on GNU/Linux. First > it relies on GNU/Linux's spelling of the ELOOP message. Second, it > relies on the fact that "echo x > p/1" will succeed if p/1 is a > dangling symlink that requires more than 20 hops to resolve. Solaris > rejects this with an ELOOP (properly, I think -- this sounds like a > Linux bug, but that's not for coreutils to fix). > > Here is a patch. > > 2007-11-16 Paul Eggert <[EMAIL PROTECTED]> > > Port readlink-fp-loop to Solaris. > * tests/misc/readlink-fp-loop (symlink_loop_msg): New var, > which records the symlink-loop message, whose wording is > not standardized by Posix. Do not rely on "echo x > p/1" > to work when p/1 has a lot of indirect symlinks. (I'm surprised > that it works on Linux. Perhaps a Linux bug?)
Hi Paul, Thanks for all the patches! I'm glad you cared enough about Solaris (8, no less!) to do all this. Regarding the number of hops, I suspect that Solaris counts differently than others, since this test passes on the *BSD-based systems, too. The way I counted (not counting symlinked-parent-dir), there were fewer than 10. I've just applied this one. _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
