RE: Ribosome build problem - need help

"Jyotsana Rathore" <[email protected]>
Newsgroups gmane.comp.multimedia.helix.devel
Message-ID <[email protected]>
Hi Chuong,

 

Your settings are correct.

What is the output of "ssh -v -l phamhuu cvs.helixcommunity.org"?

Could you also try checking out in a different folder.

 

Thanks,

Jyotsana

  _____  

From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Thursday, June 04, 2009 9:11 AM
To: [email protected];
[email protected]
Cc: [email protected]; [email protected];
[email protected]; [email protected]; [email protected];
[email protected]
Subject: [Helix-client-dev] Ribosome build problem - need help

 

 

Hi all,

 

I am encountering a severe build problem, the build with below parameters
gets stuck indefinitely after receiving some 125,568 packets from cvs
server.

[0] Set BIF branch (helix_restricted)

[1] Set Target(s) (symbianMmf_wm)

[2] Set Profile (x:\Ribosome\build\umakepf\helix-client-s60-50-mmf-mdf-dsp)

 

Ribosome has been checked out on June 3rd, 2009 with cvs -d
:ext:[email protected]:/cvsroot/ribosome co build

>From the last output of the cmd window it looks like the threads are
scheduled but never activated, the build.out log is extremely short.

[#-00000121][2009-06-04 08:32:51][4800][INFO ] : Checking out source code
and b

nary distributions.

Group size: 31  Modules: 197  Threads: 2

[#-00000149][2009-06-04 08:32:51][4800][INFO ] : Enabling threading, 2
threads

equested.

[#-00000151][2009-06-04 08:32:51][4800][INFO ] : Starting thread scheduler
to p

ocess jobs.

[#-00000184][2009-06-04 08:47:52][4800][INFO ] : Available threads:

=========== 1456 ==========

    stack:

      find @ C:\APPS\actpython\Lib\string.py # 359

      run @ x:\Ribosome\build\lib\shell.py # 726

      run @ x:\Ribosome\build\lib\shell.py # 891

      update @ x:\Ribosome\build\lib\cvs.py # 301

      update @ x:\Ribosome\build\lib\cvs.py # 400

      checkout @ x:\Ribosome\build\lib\cvs.py # 376

      Checkout @ x:\Ribosome\build\lib\cvs.py # 208

      Checkout @ x:\Ribosome\build\lib\cvs.py # 581

      Checkout @ x:\Ribosome\build\lib\cvs.py # 708

      checkout_files_from_tag @ x:\Ribosome\build\lib\buildapp.py # 1009

      checkout_module @ x:\Ribosome\build\lib\buildapp.py # 949

      run @ x:\Ribosome\build\lib\chaingang.py # 169

      doit @ x:\Ribosome\build\lib\chaingang.py # 254

      doit @ x:\Ribosome\build\lib\chaingang.py # 618

      worker @ x:\Ribosome\build\lib\chaingang.py # 263

      worker @ x:\Ribosome\build\lib\chaingang.py # 765

 

=========== 3492 ==========

    stack:

      find @ C:\APPS\actpython\Lib\string.py # 359

      run @ x:\Ribosome\build\lib\shell.py # 726

      run @ x:\Ribosome\build\lib\shell.py # 891

      update @ x:\Ribosome\build\lib\cvs.py # 301

      update @ x:\Ribosome\build\lib\cvs.py # 400

      checkout @ x:\Ribosome\build\lib\cvs.py # 376

      Checkout @ x:\Ribosome\build\lib\cvs.py # 208

      Checkout @ x:\Ribosome\build\lib\cvs.py # 581

      Checkout @ x:\Ribosome\build\lib\cvs.py # 708

      checkout_files_from_tag @ x:\Ribosome\build\lib\buildapp.py # 1009

      checkout_module @ x:\Ribosome\build\lib\buildapp.py # 949

      run @ x:\Ribosome\build\lib\chaingang.py # 169

      doit @ x:\Ribosome\build\lib\chaingang.py # 254

      doit @ x:\Ribosome\build\lib\chaingang.py # 618

      worker @ x:\Ribosome\build\lib\chaingang.py # 263

      worker @ x:\Ribosome\build\lib\chaingang.py # 765

 

I would appreciate your feedback very much.

 

Thanks,

Chuong

The SDK is Nokia pf_5250_200920. I am attaching my .build.rc, helixSet.bat
(renamed to helixSet_bat since .bat file is considered dangerous), and
build.out log file.

_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
image001.jpg (image/jpeg, 75.4 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.