Basically, jbuilder is attempting to determine if config files exist in jbuilder4/lib/ext, so that it can then load them. The bug is that when there are no config files present, (a normal condition for JB Foundation, but not normal for a complete Enterprise installation) the function attempts to read the wildcard pattern as if it were the filename. IE it's trying to open and read filename "*.config", which naturally doesn't exist.

The ls command sets an error code based on the status of the match. The problem is that the version in /usr/ucb/bin sets a different error code than all the other versions.

The bug in the script is that it does not specify a specific version of ls, instead allowing the shell to find ls on the path. If the shell finds /usr/ucb/bin/ls, the script's test of the error code will be fooled because the error code isn't the expected value.

Workaround #1:
Remove /usr/ucb/bin from your PATH before running JBuilder.

Workaround #2:
Create a one-line shell script in jbuilder4/lib/ext/foo.config, and make that one line a shell comment like this:

  # foo workaround to fix a korn script problem

Save the file, and jbuilder should now launch without difficulty.

Workaround #3:
Delete the offending /usr/ucb/bin/ls binary.

2002-Jun-15 3:03pm gyles19@visi.com