p4_Solaris10_Sparc64_2015 cannot execute binary file

[morantr]

In my organization, we must use tcsh shell. p4v doesn't work with bash. I added this to the ssh config: RemoteCommand tcsh

I created a perforce workspace using the p4 client command with a given configuration string. p4 client -i "some configuration string"

The p4v desktop app successfully identified the workspace.

When I open VS CODE it fails, this is the dump:

Performing one-time registration of perforce commands
==============================
Workspace folders changed. Starting initialisation.

Workspaces were added
> file:///auto/dev_users/mshoeg/ccm_wa/apollo/main-apollo/mainApolloWs: Trying to initialise SCM Providers in this workspace.
	Note: the following overrides apply in this workspace:
		perforce.port: none	(will not override)
		perforce.user: none	(will not override)
		perforce.client: none	(will not override)
		perforce.dir: none	(will not override)
	Explicit overrides may prevent auto-detection of other perforce client workspaces
Looking for a client root using the workspace root directory
/auto/dev_users/mshoeg/ccm_wa/apollo/main-apollo/mainApolloWs: p4 'info'
ERROR: "/sne/bin//p4: line 6: /sne/mgr/tools/Perforce_2017/p4_Solaris10_Sparc64_2015.1: cannot execute binary file\n"
ERROR: "/sne/bin//p4: line 6: /sne/mgr/tools/Perforce_2017/p4_Solaris10_Sparc64_2015.1: cannot execute binary file\n"
> file:///auto/dev_users/mshoeg/ccm_wa/apollo/main-apollo/mainApolloWs: NO CLIENT ROOT FOUND in workspace root directory
> file:///auto/dev_users/mshoeg/ccm_wa/apollo/main-apollo/mainApolloWs: Looking for perforce config files
/auto/dev_users/mshoeg/ccm_wa/apollo/main-apollo/mainApolloWs: p4 'set' '-q'
Error: /sne/bin//p4: line 6: /sne/mgr/tools/Perforce_2017/p4_Solaris10_Sparc64_2015.1: cannot execute binary file


Initialisation finished
==============================

/auto/dev_users/mshoeg/ccm_wa/apollo/main-apollo/mainApolloWs/.vscode: p4 'info'
ERROR: "/sne/bin//p4: line 6: /sne/mgr/tools/Perforce_2017/p4_Solaris10_Sparc64_2015.1: cannot execute binary file\n"
ERROR: "/sne/bin//p4: line 6: /sne/mgr/tools/Perforce_2017/p4_Solaris10_Sparc64_2015.1: cannot execute binary file\n"

Versions & Details:

• Perforce extension: 4.15.5
• VSCode version: 1.74.0
• Operating System:

> cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

• Perforce server details (if known):
• Are you using a multi-root workspace?: I Think no. not sure.

[mjcrouch]

Hi, thanks for reporting, I seem to recall I have tried it using tcsh when I was using this at the company I previously worked for and didn't have any problems. The paths etc. here seem very specific to the organization (i.e. /sne/bin/p4 and /sne/mgr/tools/Perforce_2017/p4_Solaris10_Sparc64_2015.1) and it looks like /sne/bin/p4 is some shell script that is executing a different binary. I can't really say what the problem is without knowing a lot more about your system. If you run p4 from a normal terminal does it use this command (i.e. what does which p4 return). If you run p4 from a terminal inside vs code does it have the same problem?

just looking at the output it seems like it might be trying to run a sparc64 binary on an x86 system so whatever script it is might be running the wrong binary (i.e. incorrectly determined you're on a sparc system)