You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-c-dev@ws.apache.org by "Jay Sullivan (JIRA)" <ji...@apache.org> on 2009/08/27 21:25:59 UTC
[jira] Created: (RAMPARTC-136) sec_echo fails to build
sec_echo fails to build
-----------------------
Key: RAMPARTC-136
URL: https://issues.apache.org/jira/browse/RAMPARTC-136
Project: Rampart/C
Issue Type: Bug
Components: samples
Affects Versions: 1.3.0
Environment: Ubuntu 9.04, i386 Dual Core E2200, VirtualBox VM
Reporter: Jay Sullivan
Assignee: Malinda Kaushalye Kapuruge
Priority: Blocker
After I build the Rampart/C 1.3.0 samples, it tells me "samples successfuly build. To run echo client cd to client/sec_echo and run update_n_run.sh"...so I do this:
$ cd client/sec_echo
$ sh update_n_run.sh
Copying latest module to client_repo
./update_n_run.sh: line 10: ./sec_echo: No such file or directory
The script update_n_run.sh is trying to execute "./sec_echo", which doesn't exist.The output from the samples build seems to imply that there was something wrong with libtool. I don't know what could possibly be causing this.
I've posted an article online that gives more detail on the issue: <a href="http://petio.org/2009/08/27/status.html">http://petio.org/2009/08/27/status.html</a>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (RAMPARTC-136) sec_echo fails to build
Posted by "Jay Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748914#action_12748914 ]
Jay Sullivan commented on RAMPARTC-136:
---------------------------------------
Sanjaya Ratnaweera has made the following comment:
I got the same error when I try to compile following exactly same steps as yours. But it worked when I compile rampart running build.sh instead of ./configure; make; make install. The only deference is build.sh runs ./autogen.sh before the configure script. For time being first build rampart running build.sh and compile samples after that. Anyway I think this is a bug in the pack.
> sec_echo fails to build
> -----------------------
>
> Key: RAMPARTC-136
> URL: https://issues.apache.org/jira/browse/RAMPARTC-136
> Project: Rampart/C
> Issue Type: Bug
> Components: samples
> Affects Versions: 1.3.0
> Environment: Ubuntu 9.04, i386 Dual Core E2200, VirtualBox VM
> Reporter: Jay Sullivan
> Assignee: Malinda Kaushalye Kapuruge
> Priority: Blocker
>
> After I build the Rampart/C 1.3.0 samples, it tells me "samples successfuly build. To run echo client cd to client/sec_echo and run update_n_run.sh"...so I do this:
> $ cd client/sec_echo
> $ sh update_n_run.sh
> Copying latest module to client_repo
> ./update_n_run.sh: line 10: ./sec_echo: No such file or directory
> The script update_n_run.sh is trying to execute "./sec_echo", which doesn't exist.The output from the samples build seems to imply that there was something wrong with libtool. I don't know what could possibly be causing this.
> I've posted an article online that gives more detail on the issue: http://petio.org/2009/08/27/status.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RAMPARTC-136) sec_echo fails to build
Posted by "Jay Sullivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAMPARTC-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Sullivan updated RAMPARTC-136:
----------------------------------
Description:
After I build the Rampart/C 1.3.0 samples, it tells me "samples successfuly build. To run echo client cd to client/sec_echo and run update_n_run.sh"...so I do this:
$ cd client/sec_echo
$ sh update_n_run.sh
Copying latest module to client_repo
./update_n_run.sh: line 10: ./sec_echo: No such file or directory
The script update_n_run.sh is trying to execute "./sec_echo", which doesn't exist.The output from the samples build seems to imply that there was something wrong with libtool. I don't know what could possibly be causing this.
I've posted an article online that gives more detail on the issue: http://petio.org/2009/08/27/status.html
was:
After I build the Rampart/C 1.3.0 samples, it tells me "samples successfuly build. To run echo client cd to client/sec_echo and run update_n_run.sh"...so I do this:
$ cd client/sec_echo
$ sh update_n_run.sh
Copying latest module to client_repo
./update_n_run.sh: line 10: ./sec_echo: No such file or directory
The script update_n_run.sh is trying to execute "./sec_echo", which doesn't exist.The output from the samples build seems to imply that there was something wrong with libtool. I don't know what could possibly be causing this.
I've posted an article online that gives more detail on the issue: <a href="http://petio.org/2009/08/27/status.html">http://petio.org/2009/08/27/status.html</a>
> sec_echo fails to build
> -----------------------
>
> Key: RAMPARTC-136
> URL: https://issues.apache.org/jira/browse/RAMPARTC-136
> Project: Rampart/C
> Issue Type: Bug
> Components: samples
> Affects Versions: 1.3.0
> Environment: Ubuntu 9.04, i386 Dual Core E2200, VirtualBox VM
> Reporter: Jay Sullivan
> Assignee: Malinda Kaushalye Kapuruge
> Priority: Blocker
>
> After I build the Rampart/C 1.3.0 samples, it tells me "samples successfuly build. To run echo client cd to client/sec_echo and run update_n_run.sh"...so I do this:
> $ cd client/sec_echo
> $ sh update_n_run.sh
> Copying latest module to client_repo
> ./update_n_run.sh: line 10: ./sec_echo: No such file or directory
> The script update_n_run.sh is trying to execute "./sec_echo", which doesn't exist.The output from the samples build seems to imply that there was something wrong with libtool. I don't know what could possibly be causing this.
> I've posted an article online that gives more detail on the issue: http://petio.org/2009/08/27/status.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.