Yes, long time ago and again yesterday before new attempt on a colleague's recommendation.
After clicking on agree the webpage https://helixcommunity.org/projects/distribution/files pops up.
Is there some special project I need to register to?
Thanks,
Chuong
________________________________
From: ext Jyotsana Rathore [mailto:[email protected]]
Sent: Thursday, June 04, 2009 5:05 PM
To: Pham-Huu Chuong (Nokia-D-MSW/Dallas); [email protected]; [email protected]
Cc: Jiau Arnold (Nokia-D-MSW/Dallas); Adookkattil Saleem (Nokia-D-MSW/Dallas); Fu Liz (EXT-DextraTech-MSW/Dallas); Ren Jun (Nokia-D-MSW/Dallas); Yu I-Chin (Nokia-D-MSW/Dallas); Srivastava Asheesh (EXT-Infovision-MSW/Dallas); Shetty Girish (Nokia-D-MSW/Dallas); Liu Junhong (Nokia-D-MSW/Dallas)
Subject: RE: Ribosome build problem - need help
Hi Chuong,
Have you agreed to the BUELA yet: https://helixcommunity.org/beula/
Thanks,
Jyotsana
________________________________
From: [email protected] [mailto:[email protected]]
Sent: Thursday, June 04, 2009 2:20 PM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: RE: Ribosome build problem - need help
Hi all,
A look into the last created log file under folder ribisome_logs points to a distribution problem.
What could the fix be? Is it an access right issue?
Thanks,
Chuong
#-00000097][2009-06-04 14:32:21][5016][INFO ] : Building filename lists.
[#-00000104][2009-06-04 14:32:21][5016][INFO ] : Parsing BIF "X:\helix\build\bif-cvs\helix\common-restricted/build/BIF\helix_restricted.bif"
[#-00000114][2009-06-04 14:32:21][5016][INFO ] : Using target 'phonon_backend' from bif 'X:\helix\build\bif-cvs\helix\common-restricted/build/BIF\helix_restricted.bif'.
[#-00000115][2009-06-04 14:32:21][5016][INFO ] : Building dependency tree for targets.
[#-00000121][2009-06-04 14:32:21][5016][INFO ] : Checking out source code and binary distributions.
[#-00000149][2009-06-04 14:32:22][5016][INFO ] : Enabling threading, 2 threads requested.
[#-00000151][2009-06-04 14:32:22][5016][INFO ] : Starting thread scheduler to process jobs.
[#-00000182][2009-06-04 14:32:22][5200][INFO ] : TESTING distribution/symbian-91-armv5/helix-client-s60-ng
[#-00000186][2009-06-04 14:32:22][5200][INFO ] : RESULT => False
[#-00000207][2009-06-04 14:32:22][5200][INFO ] : TESTING distribution/symbian-91-armv5/helix-client-s60-ng-
[#-00000211][2009-06-04 14:32:22][5200][INFO ] : RESULT => False
[#-00000232][2009-06-04 14:32:22][5200][INFO ] : TESTING distribution/symbian-91-armv5/helix-client-s60-
[#-00000236][2009-06-04 14:32:22][5200][INFO ] : RESULT => False
[#-00000257][2009-06-04 14:32:22][5200][INFO ] : TESTING distribution/symbian-91-armv5/helix-client-
[#-00000261][2009-06-04 14:32:22][5200][INFO ] : RESULT => False
[#-00000282][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5/helix-
[#-00000286][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
[#-00000306][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5/release
[#-00000310][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
[#-00000320][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5
[#-00000324][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
[#-00000336][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5-/helix-client-s60-ng
[#-00000340][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
[#-00000361][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5-/helix-client-s60-ng-
[#-00000365][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
[#-00000386][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5-/helix-client-s60-
[#-00000390][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
[#-00000411][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5-/helix-client-
[#-00000415][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
[#-00000436][2009-06-04 14:32:23][5200][INFO ] : TESTING distribution/symbian-91-armv5-/helix-
[#-00000440][2009-06-04 14:32:23][5200][INFO ] : RESULT => False
_____________________________________________
From: Pham-Huu Chuong (Nokia-D-MSW/Dallas)
Sent: Thursday, June 04, 2009 11:11 AM
To: [email protected]; [email protected]
Cc: Jiau Arnold (Nokia-D-MSW/Dallas); Adookkattil Saleem (Nokia-D-MSW/Dallas); Fu Liz (EXT-DextraTech-MSW/Dallas); Ren Jun (Nokia-D-MSW/Dallas); Yu I-Chin (Nokia-D-MSW/Dallas); Srivastava Asheesh (EXT-Infovision-MSW/Dallas); Shetty Girish (Nokia-D-MSW/Dallas); Liu Junhong (Nokia-D-MSW/Dallas)
Subject: 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.
<< File: Copy of .buildrc >> << File: helixSet_bat >> << File: build1.out >>
<< OLE Object: Picture (Device Independent Bitmap) >>
_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
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.