Brian K. White wrote:
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.
No...I was driving home a point. Although common, "configure" is a not a standard program
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 ?
Configure doesn't know diddly squat about an environment.. that's why it runs a million tests trying to figure out just what is and is not there, and what capabilities the system has, before trying to even create a Makefile, and usually, determine which CFLAGS to mandate, etc.
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.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org