Consider the implications of this for a while: Why does ./configure run an empirical test, trying progressively larger and larger command lines until it breaks?
which "configure" is that?
$ which configure $
Hmmm... it seems that "configure" is *NOT* a standard command.
What do you think about that?
I think anyone who sees dot-slash-configure and pretends not to know what it refers to has lost the focus of the discussion. Or if they really don't know then they are not qualified to have any opinion in this discussion. Sure, a lot of unix happened before 1991 when autoconf was first created, but is a person who got very experienced but then dropped out in '91 so thoroughly that they never enountered ./configure in the next _17_ years likely to be on an opensuse mail list ? I agree completely that within any particular bag of tools sold as part of one kit under one name will generally all adhere to the same set of limits across the board. I was pointedly alluding to code and/or bins that may not come from the same source as this or that particular xargs binary. Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org