[
https://issues.apache.org/jira/browse/JENA-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105071#comment-15105071
]
ASF subversion and git services commented on JENA-1120:
-------------------------------------------------------
Commit 35e964a5eb99e15c479c67f81f5e414105b3a64a in jena's branch
refs/heads/master from [~osma]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=35e964a ]
JENA-1120: set interpreter to /bin/bash because script contains bashisms
> bashisms in jena-sdb/bin/make_classpath
> ---------------------------------------
>
> Key: JENA-1120
> URL: https://issues.apache.org/jira/browse/JENA-1120
> Project: Apache Jena
> Issue Type: Bug
> Components: SDB
> Affects Versions: Jena 3.0.1
> Environment: Ubuntu 12.04
> Reporter: Osma Suominen
> Assignee: Osma Suominen
> Fix For: Jena 3.1.0
>
>
> The script make_classpath is called indirectly by the SDB command line
> utilities. The shebang line sets it to be interpreted using /bin/sh but parts
> of the script seem to rely on bash-specific features. On Ubuntu and Debian
> systems at least, /bin/sh is nowadays often symlinked to dash which only
> implements the POSIX standard parts (see https://wiki.ubuntu.com/DashAsBinSh
> for background).
> This leads to errors such as this one:
> {noformat}
> $ sdbinfo
> /home/oisuomin/sw/jena-sdb-3.1.0-SNAPSHOT/bin/make_classpath: 63:
> /home/oisuomin/sw/jena-sdb-3.1.0-SNAPSHOT/bin/make_classpath: Bad substitution
> Error: Could not find or load main class sdb.sdbinfo
> {noformat}
> The simple fix is to change the interpreter to /bin/bash and I will do that
> very soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
