On Aug 22, 2006, at 11:49 AM, Knut Lorenzen wrote:
Tim Jones schrieb dereinst (am 22.08.2006 20:02 Uhr) via
[EMAIL PROTECTED]:
Tiger **WON'T** execute fat binary command line tools such as grep,
cat, sudo ...
I don't see this.
pc-00179:~ tjones$ sh grep -a tiger1 /etc/hosts
grep: /usr/bin/grep: cannot execute binary file
True, the first argument of "sh" is assumed to be the name of a file
containing shell commands, not a binary like grep. What you want is
probably
sh -c "grep -a tiger1 /etc/hosts"
I see this now - I've rebooted my Mac Pro because a lot of OTHER
stuff started acting strangely.
The reason for my jump to this conclusion is that it would also
happen if I started my Terminal session with /bin/sh as my shell.
However, it doesn't change the fact that I still see the errors under
the Shell class when running an app. If the exec'd tool is either a
separate power-pc or i386 binary, the error doesn't occur with no
other changes to my RB code, so something is still amiss.
Tim
--
Tim Jones [EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
