[K42-discussion] problems with kcvs?

Livio Soares livio at eecg.toronto.edu
Tue Nov 1 08:04:50 EST 2005


  Hi Bob,

  Please be  aware that we "outsider's"  checkout from kcvs  repository; not the
one on kix. Look at the CVSROOT/modules on kcvs:

kitchsrc -a  kitch-core kitch-linux kitch-thin k42-pem-tools khwtools dyn-up-tools k42-trace-xml
                                                                      ^^^^^^^^^^^^^

  I think the cvs client bails out when it cannot find 'dyn-up-tools' module (it
is _not_ on kcvs).  If Watson doesn't want to release the 'dyn-up-tools' module,
I suggest two options:

1) remove it completely from the CVSROOT/modules file

2) Leave 'dyn-up-tools' module as the last  on the list.  This way cvs will exit
   trying to checkout  the dyn-up-tools module only after  getting all the other
   modules.

  For the  people outside  of Watson,  I suggest just  checking out  the missing
module manually; so do the traditional checkout first:

cvs -d cvs at kcvs:/u/kitchawa/cvsroot co kitchsrc

   and force the checkout of k42-trace-xml

cvs -d cvs at kcvs:/u/kitchawa/cvsroot co k42-trace-xml

  (don't change directories in between commands). 

  I think doing this gets you a complete/clean tree.

  Hope this helps,

				Livio

Robert Wisniewski writes:
> Okay - this is something I should look at.  The odd thing is that no one
> here is reporting the problem.  I can not think of a reason why there would
> be a problem with traceUser.xml.  Would it be possible to set up a vnc
> server so I can observe the problem and poke around the source tree.  I
> would have a little time tomorrow (Tues 11-1) to look at the problem.
> Hopefully the issue would be the same as Philip's.
> 
> -bob
> 
> Robert Wisniewski
> The K42 MP OS Project
> Advanced Operating Systems
> IBM T.J. Watson Research Center
> 914-945-3181
> http://www.research.ibm.com/K42/
> bob at watson.ibm.com
> 
> ----
> 
> Alex Depoutovitch writes:
>  > I also have this error.
>  > Does anybody know how to solve it, as newly checked out source tree
>  > can not be built.
>  > Thank you,
>  > Alex
>  > 
>  > On 10/7/05, Kurt Ferreira <kurt at cs.unm.edu> wrote:
>  > > Hey All,
>  > >
>  > > On Fri, 7 Oct 2005, Edgar Leon wrote:
>  > >
>  > > > Hello Livio,
>  > > >
>  > > > It seems that the warning/errors are not so harmless. When I try to build I
>  > > > get (note that this is a fresh checkout of the code, not an update):
>  > > >
>  > > > kinstall: ./ -> /home/leon/k42test/install/include/sync/ :
>  > > >   - RequestCount.H
>  > > > make[6]: Entering directory
>  > > > `/home/leon/k42test/powerpc/partDeb/lib/libc/trace'
>  > > > make[6]: *** No rule to make target `k42-trace-xml/traceUser.xml'.  Stop.
>  > > > make[6]: Leaving directory `/home/leon/k42test/powerpc/partDeb/lib/libc/trace'
>  > > > make[5]: *** [k42-trace-xml/traceUser.xml] Error 2
>  > > >
>  > > > Kurt has also encounter this issue and has a fix for it, but I will let him
>  > > > talk about it.
>  > > >
>  > > Not a fix but I worked around for us to continue here at UNM :)
>  > > (unfortunatly I ran into this weeks ago and forgot to mention, oopps got
>  > > busy)
>  > >
>  > > If you do an update (as Edgar stated) you do not run into this problem.
>  > > If you do a fresh chechout the XML files do not seem to be checked out
>  > > possibly related to error Edgar posted.  For us to work around I just
>  > > grabbed an older copy of the xml dir and hand modified a few CVS files to
>  > > the get CVS to update the these XML files (A solution looks like it
>  > > involves fixing things on the kcvs end).
>  > >
>  > > Now that I think of it, the last update I performed also required me to
>  > > change the config for linux.  Let me verify that change did not have
>  > > anything to do with stuff I am doing locally.
>  > >
>  > > THX
>  > > kurt
>  > > _______________________________________________
>  > > K42-discussion mailing list
>  > > K42-discussion at ozlabs.org
>  > > https://ozlabs.org/mailman/listinfo/k42-discussion
>  > >
>  > _______________________________________________
>  > K42-discussion mailing list
>  > K42-discussion at ozlabs.org
>  > https://ozlabs.org/mailman/listinfo/k42-discussion
>  > 
> _______________________________________________
> K42-discussion mailing list
> K42-discussion at ozlabs.org
> https://ozlabs.org/mailman/listinfo/k42-discussion
> 



More information about the K42-discussion mailing list