On Tuesday, June 25, 2002, at 12:05 PM, Nicola Pero wrote: > No reason not to use it ... but would it fix the problem ? > > I think his problem was that he needed /bin/test to be executed instead > of > the built-in test.
Exactly. > Would using test rather [...] solve the problem, or would the built-in > test still be used ? It would. You definitely need to use /bin/sh on Solaris 8. znek@lestat:(~)$ uname -a SunOS lestat 5.8 Generic_108528-14 sun4u sparc SUNW,UltraSPARC-IIi-Engine > I would assume - if it's a reasonable shell - the built-in test would > still be used :-) Correct. That's what it does. I was thinking about something in config.make like TEST=test for all architectures except Solaris and TEST=/bin/test for Solaris. It conflicts with Nicola's otherwise well-thought argument to not use absolute paths, though. I don't know of any architectures except Solaris where it does make sense to use absolute paths, but Solaris still ships with many broken tools (awk to name one) that it almost seems necessary to provide at least some reasonable defaults for basic Solaris installations (the machine above happens to be almost clean, which gave me certain pains in the ass, I almost forgot how bug-ridden the default userland on that OS is). Cheers, Marcus -- Marcus Mueller . . . crack-admin/coder ;-) Mulle kybernetiK . http://www.mulle-kybernetik.com Current projects: finger [EMAIL PROTECTED] _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
