Has anyone executed antsetenv.sh on latest version of macOS Sierra?

[Former Member]

When I execute . ./setantenv.sh .

I'm getting;
.: Command not found.

If I try to run as:
source ./setantenv.sh

I am getting:
OWN_NAME=setantenv.sh: Command not found. OWN_NAME: Undefined variable.

I've not seen this happen on previous versions of macOS / OSX.
This is on hybris 6.x

[Former Member · Accepted solution]

It turns out that SAP changed my default shell to the CSH shell when configuring my MacBook (or Apple changed the default on the Sierra vanilla install). I have changed it back to /bin/bash and this now works.

Looks like CSH shell doesn't support the . alias for source . ./ whereas bash does.

[Former Member · Accepted solution]

Hi, I guess it is not SAP who has changed the default shell ;-) I noticed that general new MacBooks use CSH as the default in the Terminal application.

Cheers, Thomas

[Former Member · Accepted solution]

Didn't bash used to be the default?

[former_member626360]

This happened to me on mac OS sierra. Reason was file setantenv.sh doesnt have execute permissions. Did chmod -777 setantenv.sh . It solved the problem.

[takahiro_kitazume]

Yes, it works fine for me.

localhost:platform mymac$ sw_vers

ProductName: Mac OS X

ProductVersion: 10.12.3

BuildVersion: 16D32

localhost:platform mymac$ . ./setantenv.sh

Did you check execution right is properly assigned to your setantenv.sh? Perhaps permissions got modified. I recall when you upgrade Sierra, some of permissions has been modified and I had other issues.

[Former Member]

The setantenv.sh script does a chmod -x if you try to run the script like ./setantenv.sh so it's not supposed to be executable in the first place. What other permissions are you referring to? The current permissions are set as -rw-r--r--@ this is fine and it executes perfectly on el capitan but not on sierra. I can't see what other difference in the local environment might cause this.

[Former Member]

This looks like a more general problem where I'm unable to execute any shell script using . ./ where as ./ and source ./ works fine. Definitely something wrong with my local environment.