You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2008/05/20 10:04:55 UTC
[jira] Created: (QPID-1076) Cannot run Java Broker from trunk
release due to qpid-run error
Cannot run Java Broker from trunk release due to qpid-run error
---------------------------------------------------------------
Key: QPID-1076
URL: https://issues.apache.org/jira/browse/QPID-1076
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: M3
Reporter: Marnie McCormack
Assignee: Marnie McCormack
Fix For: M3
$ ./qpid-server
qpid-run: line 20: $'\r': command not found
qpid-run: line 27: syntax error near unexpected token `$'{\r''
'pid-run: line 27: `die() {
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1076) Cannot run Java Broker built on cygwin
from trunk release due to qpid-run format issue
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-1076:
-----------------------------------
Description:
$ ./qpid-server
qpid-run: line 20: $'\r': command not found
qpid-run: line 27: syntax error near unexpected token `$'{\r''
'pid-run: line 27: `die() {
qpid-run in dos format if build on cygwin. Oddly not all the .sh files suffer this consequence, including qpid-server. Looks like this is to do with .sh files have native eol and non-sh suffixed files coming out ok. Will look some more and propose a solution which will allow us to build (ant release) successfully on cygwin.
was:
$ ./qpid-server
qpid-run: line 20: $'\r': command not found
qpid-run: line 27: syntax error near unexpected token `$'{\r''
'pid-run: line 27: `die() {
Summary: Cannot run Java Broker built on cygwin from trunk release due to qpid-run format issue (was: Cannot run Java Broker from trunk release due to qpid-run error)
> Cannot run Java Broker built on cygwin from trunk release due to qpid-run format issue
> --------------------------------------------------------------------------------------
>
> Key: QPID-1076
> URL: https://issues.apache.org/jira/browse/QPID-1076
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M3
> Reporter: Marnie McCormack
> Assignee: Marnie McCormack
> Fix For: M3
>
>
> $ ./qpid-server
> qpid-run: line 20: $'\r': command not found
> qpid-run: line 27: syntax error near unexpected token `$'{\r''
> 'pid-run: line 27: `die() {
> qpid-run in dos format if build on cygwin. Oddly not all the .sh files suffer this consequence, including qpid-server. Looks like this is to do with .sh files have native eol and non-sh suffixed files coming out ok. Will look some more and propose a solution which will allow us to build (ant release) successfully on cygwin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (QPID-1076) Cannot run Java Broker built on cygwin
from trunk release due to qpid-run format issue
Posted by "Aidan Skinner (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aidan Skinner resolved QPID-1076.
---------------------------------
Resolution: Fixed
This wfm now! Woo!
> Cannot run Java Broker built on cygwin from trunk release due to qpid-run format issue
> --------------------------------------------------------------------------------------
>
> Key: QPID-1076
> URL: https://issues.apache.org/jira/browse/QPID-1076
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M3
> Reporter: Marnie McCormack
> Assignee: Marnie McCormack
> Fix For: M3
>
>
> $ ./qpid-server
> qpid-run: line 20: $'\r': command not found
> qpid-run: line 27: syntax error near unexpected token `$'{\r''
> 'pid-run: line 27: `die() {
> qpid-run in dos format if build on cygwin. Oddly not all the .sh files suffer this consequence, including qpid-server. Looks like this is to do with .sh files have native eol and non-sh suffixed files coming out ok. Will look some more and propose a solution which will allow us to build (ant release) successfully on cygwin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.