cvs seg faults when creating a new project
with object files or symbolic links in the
directory tree.
Cheers
Angus
Angus Ainslie <angusa@deltatee.com> wrote:
cvs seg faults when creating a new project
with object files or symbolic links in the
directory tree.
Do you mean when you do a cvs add?
No when I create the repository.
cvs import -m “New driver” emscan/driver emscan start
Colin Burgess wrote:
Angus Ainslie <> angusa@deltatee.com> > wrote:
cvs seg faults when creating a new project
with object files or symbolic links in the
directory tree.Do you mean when you do a cvs add?
Angus Ainslie <angusa@deltatee.com> wrote:
No when I create the repository.
cvs import -m “New driver” emscan/driver emscan start
Ah. The problem is that cvs import is busted under RTP. You can get a fixed
version at http://staff.qnx.com/~cburgess/cvs
Colin Burgess wrote:
Angus Ainslie <> angusa@deltatee.com> > wrote:
cvs seg faults when creating a new project
with object files or symbolic links in the
directory tree.Do you mean when you do a cvs add?
Is that going to be fixed in the next patch ?
Colin Burgess wrote:
Angus Ainslie <> angusa@deltatee.com> > wrote:
No when I create the repository.cvs import -m “New driver” emscan/driver emscan start
Ah. The problem is that cvs import is busted under RTP. You can get a fixed
version at > http://staff.qnx.com/~cburgess/cvsColin Burgess wrote:
Angus Ainslie <> angusa@deltatee.com> > wrote:
cvs seg faults when creating a new project
with object files or symbolic links in the
directory tree.Do you mean when you do a cvs add?
I tried the URL you specified and got a bunch of garbage characters. I then
tried it under with Voyager under Phindows and it locked up my
Phindows session.
Also, any plans to support the “server access method” of cvs anytime soon?
Sylvain Marcotte
Colin Burgess <cburgess@qnx.com> wrote in message
news:97199u$7ec$1@nntp.qnx.com…
Angus Ainslie <> angusa@deltatee.com> > wrote:
No when I create the repository.cvs import -m “New driver” emscan/driver emscan start
Ah. The problem is that cvs import is busted under RTP. You can get a
fixed
version at > http://staff.qnx.com/~cburgess/cvsColin Burgess wrote:
Angus Ainslie <> angusa@deltatee.com> > wrote:
cvs seg faults when creating a new project
with object files or symbolic links in the
directory tree.Do you mean when you do a cvs add?
Sylvain Marcotte <smarcotte@vortek.com> wrote:
I tried the URL you specified and got a bunch of garbage characters. I then
tried it under with Voyager under Phindows and it locked up my
Phindows session.
Sorry, go to http://staff.qnx.com/~cburgess/freestuff
Also, any plans to support the “server access method” of cvs anytime soon?
??? OUr cvs already supports this - it’s what we use internally.
Or do you mean where is the server?
We use a Linux box as our CVS server and set it up so that the CVS clients
use rsh to get the files out of it.
ie CVSROOT=:server:LINUXCOMPUTER:/ourrepository. This is the prescribed CVS
way and it works with the WinCVS and CVS on Windows
and Linux. Now if try that method under QNX6 and try to checkout a module, I
get the following message
“cvs [checkout aborted]: the :server: access method is not supported by this
port of CVS”
So we end up having to mount the repository drive from our QNX6 computers so
that we can access our repository. Doing it this way prevents
some of the scripts from the CVSROOT admin files to execute cause they
expect to run on a Linux box.
Any chance of that working anytime soon?
Which way do you guys use?
Sylvain
Colin Burgess <cburgess@qnx.com> wrote in message
news:974496$rip$1@nntp.qnx.com…
Sylvain Marcotte <> smarcotte@vortek.com> > wrote:
I tried the URL you specified and got a bunch of garbage characters. I
then
tried it under with Voyager under Phindows and it locked up my
Phindows session.Sorry, go to > http://staff.qnx.com/~cburgess/freestuff
Also, any plans to support the “server access method” of cvs anytime
soon???? OUr cvs already supports this - it’s what we use internally.
Or do you mean where is the server?
You should use the :ext: method - the :server: method assumes a builtin
rsh method. SInce QNX has an external rsh, it uses that instead.
Note that we use the :pserver: method internally.
Also note that you will have to have rsh working correctly. Try
rsh LINUXCOMPUTER /bin/ls
first.
Sylvain Marcotte <smarcotte@vortek.com> wrote:
We use a Linux box as our CVS server and set it up so that the CVS clients
use rsh to get the files out of it.
ie CVSROOT=:server:LINUXCOMPUTER:/ourrepository. This is the prescribed CVS
way and it works with the WinCVS and CVS on Windows
and Linux. Now if try that method under QNX6 and try to checkout a module, I
get the following message
“cvs [checkout aborted]: the :server: access method is not supported by this
port of CVS”
So we end up having to mount the repository drive from our QNX6 computers so
that we can access our repository. Doing it this way prevents
some of the scripts from the CVSROOT admin files to execute cause they
expect to run on a Linux box.
Any chance of that working anytime soon?
Which way do you guys use?
Sylvain
Colin Burgess <> cburgess@qnx.com> > wrote in message
news:974496$rip$> 1@nntp.qnx.com> …
Sylvain Marcotte <> smarcotte@vortek.com> > wrote:
I tried the URL you specified and got a bunch of garbage characters. I
then
tried it under with Voyager under Phindows and it locked up my
Phindows session.Sorry, go to > http://staff.qnx.com/~cburgess/freestuff
Also, any plans to support the “server access method” of cvs anytime
soon???? OUr cvs already supports this - it’s what we use internally.
Or do you mean where is the server?
Thank’s. That did the trick.
Colin Burgess <cburgess@qnx.com> wrote in message
news:974jme$64h$1@nntp.qnx.com…
You should use the :ext: method - the :server: method assumes a builtin
rsh method. SInce QNX has an external rsh, it uses that instead.Note that we use the :pserver: method internally.
Also note that you will have to have rsh working correctly. Try
rsh LINUXCOMPUTER /bin/ls
first.Sylvain Marcotte <> smarcotte@vortek.com> > wrote:
We use a Linux box as our CVS server and set it up so that the CVS
clients
use rsh to get the files out of it.
ie CVSROOT=:server:LINUXCOMPUTER:/ourrepository. This is the prescribed
CVS
way and it works with the WinCVS and CVS on Windows
and Linux. Now if try that method under QNX6 and try to checkout a
module, I
get the following message
“cvs [checkout aborted]: the :server: access method is not supported by
this
port of CVS”
So we end up having to mount the repository drive from our QNX6
computers so
that we can access our repository. Doing it this way prevents
some of the scripts from the CVSROOT admin files to execute cause they
expect to run on a Linux box.
Any chance of that working anytime soon?
Which way do you guys use?
Sylvain
Colin Burgess <> cburgess@qnx.com> > wrote in message
news:974496$rip$> 1@nntp.qnx.com> …
Sylvain Marcotte <> smarcotte@vortek.com> > wrote:
I tried the URL you specified and got a bunch of garbage characters.
I
then
tried it under with Voyager under Phindows and it locked up my
Phindows session.Sorry, go to > http://staff.qnx.com/~cburgess/freestuff
Also, any plans to support the “server access method” of cvs anytime
soon???? OUr cvs already supports this - it’s what we use internally.
Or do you mean where is the server?
–
cburgess@qnx.com
\