Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DSDP - Real-Time Software Components (RTSC) » Problem with RTSC module primer lesson 5
Problem with RTSC module primer lesson 5 [message #666709] Thu, 21 April 2011 18:38 Go to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
Hello,

In lesson 5, I can run 'xdc all' without any problems, but when I try to test the package, I get the following:

D:\examples\lesson5>xdc test
C:/Users/SEBAST~1/AppData/Local/Temp/make4244-1.sh: 1: Syntax error: "(" unexpected
xdctools_3_20_03_63\gmake.exe: *** [prog.x64P.test] Error 2


Why is this happening? Can you help me?

Regards.
Re: Problem with RTSC module primer lesson 5 [message #667268 is a reply to message #666709] Wed, 27 April 2011 18:22 Go to previous messageGo to next message
Sasha Slijepcevic is currently offline Sasha SlijepcevicFriend
Messages: 90
Registered: July 2009
Member
Sebastian,
there was a bug in the platform that was used by default to run the examples. We fixed the bug since the 3.20.03 release, but just to be sure that's the problem you are seeing, can you add XDCOPTIONS=v to your xdc command line?
xdc XDCOPTIONS=v test


That should print the actual command line that runs the test, and I might be able to tell you how to fix it, or update your XDCtools installation.

Alternatively, look for the line in your config.bld, one directory above lesson5 and find the line:
C64P.platform = 'ti.platforms.load6x';

Try replacing that line with
C64P.platform = 'ti.platforms.sim64Pxx';

and see if that helps.
Re: Problem with RTSC module primer lesson 5 [message #667403 is a reply to message #667268] Thu, 28 April 2011 14:44 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
Sasha,

Thanks for your response.

Adding XDCOPTIONS=v to my xdc command does not make the output different. However, if I use

xdc clean
xdc XDCOPTIONS=v all


I get the following:
#
# making package.mak (because of package.bld) ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/xs  -Dxdc.path="C:/PROGRA~2/TEXASI~1/xd
ctools_3_20_03_63/packages;.." -Dxdc.root=C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_
63 -Dxdc.hostOS=Windows -Dconfig.importPath=".;C:/PROGRA~2/TEXASI~1/xdctools_3_2
0_03_63/packages;..;C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63;C:/PROGRA~2/TEXASI~
1/xdctools_3_20_03_63/etc" -Dxdc.bld.targets="" -DTOOLS=   -f C:/PROGRA~2/TEXASI
~1/xdctools_3_20_03_63/packages/xdc/bld/bld.js ../config.bld package.bld package
.mak
#
# generating interfaces for package lesson5 (because package/package.xdc.inc is
older than package.xdc) ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/xs -Dxdc.path="C:/PROGRA~2/TEXASI~1/xdc
tools_3_20_03_63/packages;.." -Dxdc.root=C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_6
3 -Dxdc.hostOS=Windows -Dconfig.importPath=".;C:/PROGRA~2/TEXASI~1/xdctools_3_20
_03_63/packages;..;C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63;C:/PROGRA~2/TEXASI~1
/xdctools_3_20_03_63/etc" -Dxdc.bld.targets="" -DTOOLS=  -f xdc/services/intern/
cmd/build.xs  -m package/package.xdc.dep -i package/package.xdc.inc package.xdc
#
# configuring prog.x64P from package/cfg/prog_x64P.cfg ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/xs -Dxdc.path="C:/PROGRA~2/TEXASI~1/xdc
tools_3_20_03_63/packages;.." -Dxdc.root=C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_6
3 -Dxdc.hostOS=Windows -Dconfig.importPath=".;C:/PROGRA~2/TEXASI~1/xdctools_3_20
_03_63/packages;..;C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63;C:/PROGRA~2/TEXASI~1
/xdctools_3_20_03_63/etc" -Dxdc.bld.targets="" -DTOOLS=   xdc.cfg prog.x64P pack
age/cfg/prog_x64P.cfg package/cfg/prog_x64P
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg/prog/prog.o64P
#
# cl64P prog.c ...
C:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/bin/cl6x -c  -qq -pdsw225 -mv64p
 -eo.o64P -ea.s64P   -Dxdc_cfg__header__='lesson5/package/cfg/prog_x64P.h'  -Dxd
c_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_bld__profile_re
lease -Dxdc_bld__vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~1/xdctools_3_20_03
_63/packages -I.. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/include -fs=
./package/cfg/prog -fr=./package/cfg/prog -fc prog.c
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/mkdep -a package/cfg/prog/prog.o64P
.dep -p package/cfg/prog -s o64P prog.c -C   -qq -pdsw225 -mv64p -eo.o64P -ea.s6
4P   -Dxdc_cfg__header__='lesson5/package/cfg/prog_x64P.h'  -Dxdc_target_name__=
C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_bld__profile_release -Dxdc_bld_
_vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/packages -I.
. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/include -fs=./package/cfg/pr
og -fr=./package/cfg/prog
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg/prog_x64P.o64P
#
# cl64P package/cfg/prog_x64P.c ...
C:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/bin/cl6x -c  -qq -pdsw225 -mo --
no_compress -mv64p -eo.o64P -ea.s64P   -Dxdc_cfg__header__='lesson5/package/cfg/
prog_x64P.h'  -Dxdc_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dx
dc_bld__profile_release -Dxdc_bld__vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~
1/xdctools_3_20_03_63/packages -I.. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/
c6000/include -fs=./package/cfg -fr=./package/cfg -fc package/cfg/prog_x64P.c
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/mkdep -a package/cfg/prog_x64P.o64P
.dep -p package/cfg -s o64P package/cfg/prog_x64P.c -C   -qq -pdsw225 -mo --no_c
ompress -mv64p -eo.o64P -ea.s64P   -Dxdc_cfg__header__='lesson5/package/cfg/prog
_x64P.h'  -Dxdc_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_b
ld__profile_release -Dxdc_bld__vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~1/xd
ctools_3_20_03_63/packages -I.. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c600
0/include -fs=./package/cfg -fr=./package/cfg
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f prog.x64P
#
# lnk64P prog.x64P ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg//prog.x64P.map
C:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/bin/lnk6x -w -q -u _c_int00  -q
-o prog.x64P package/cfg/prog/prog.o64P package/cfg/prog_x64P.o64P  package/cfg/
prog_x64P.xdl  -c -m package/cfg//prog.x64P.map -l C:/PROGRA~2/TEXASI~1/ccsv4/to
ols/compiler/c6000/lib/rts64plus.lib
#
# configuring prog.x86GW from package/cfg/prog_x86GW.cfg ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/xs -Dxdc.path="C:/PROGRA~2/TEXASI~1/xdc
tools_3_20_03_63/packages;.." -Dxdc.root=C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_6
3 -Dxdc.hostOS=Windows -Dconfig.importPath=".;C:/PROGRA~2/TEXASI~1/xdctools_3_20
_03_63/packages;..;C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63;C:/PROGRA~2/TEXASI~1
/xdctools_3_20_03_63/etc" -Dxdc.bld.targets="" -DTOOLS=   xdc.cfg prog.x86GW pac
kage/cfg/prog_x86GW.cfg package/cfg/prog_x86GW
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg/prog/prog.o86GW
#
# cl86GW prog.c ...
C:/MinGW//bin/mingw32-gcc.exe -c  -x c  -O2  -Dfar=   -Dxdc_cfg__header__='lesso
n5/package/cfg/prog_x86GW.h'  -Dxdc_target_name__=Mingw -Dxdc_target_types__=gnu
/targets/std.h -Dxdc_bld__profile_release -Dxdc_bld__vers_1_0_4_5_2 -O2 -ffuncti
on-sections -fdata-sections  -I. -IC:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/pack
ages -I..  -o package/cfg/prog/prog.o86GW prog.c
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/mkdep -o package/cfg/prog/prog.o86G
W.dep -p package/cfg/prog/ -s o86GW prog.c -C -O2  -Dfar=   -Dxdc_cfg__header__=
'lesson5/package/cfg/prog_x86GW.h'  -Dxdc_target_name__=Mingw -Dxdc_target_types
__=gnu/targets/std.h -Dxdc_bld__profile_release -Dxdc_bld__vers_1_0_4_5_2 -O2 -f
function-sections -fdata-sections  -I. -IC:/PROGRA~2/TEXASI~1/xdctools_3_20_03_6
3/packages -I..
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg/prog_x86GW.o86GW
#
# cl86GW package/cfg/prog_x86GW.c ...
C:/MinGW//bin/mingw32-gcc.exe -c  -x c  -O2  -Dfar=   -Dxdc_cfg__header__='lesso
n5/package/cfg/prog_x86GW.h'  -Dxdc_target_name__=Mingw -Dxdc_target_types__=gnu
/targets/std.h -Dxdc_bld__profile_release -Dxdc_bld__vers_1_0_4_5_2 -O2 -ffuncti
on-sections -fdata-sections  -I. -IC:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/pack
ages -I..  -o package/cfg/prog_x86GW.o86GW package/cfg/prog_x86GW.c
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/mkdep -o package/cfg/prog_x86GW.o86
GW.dep -p package/cfg/ -s o86GW package/cfg/prog_x86GW.c -C -O2  -Dfar=   -Dxdc_
cfg__header__='lesson5/package/cfg/prog_x86GW.h'  -Dxdc_target_name__=Mingw -Dxd
c_target_types__=gnu/targets/std.h -Dxdc_bld__profile_release -Dxdc_bld__vers_1_
0_4_5_2 -O2 -ffunction-sections -fdata-sections  -I. -IC:/PROGRA~2/TEXASI~1/xdct
ools_3_20_03_63/packages -I..
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f prog.x86GW
#
# lnk86GW prog.x86GW ...
C:/MinGW//bin/mingw32-gcc.exe    -o prog.x86GW package/cfg/prog/prog.o86GW packa
ge/cfg/prog_x86GW.o86GW  package/cfg/prog_x86GW.xdl  -lstdc++ -LC:/MinGW/lib
#
# all files complete.

Maybe this helps to track the problem.

On the other hand, config.bld already has
C64P.platform = 'ti.platforms.sim64Pxx';


So what should I do now? Any ideas?
Thanks for your help.
Re: Problem with RTSC module primer lesson 5 [message #667605 is a reply to message #667403] Fri, 29 April 2011 21:33 Go to previous messageGo to next message
Sasha Slijepcevic is currently offline Sasha SlijepcevicFriend
Messages: 90
Registered: July 2009
Member
If you run:
xdc clean
xdc XDCOPTIONS=v test

there should be a line that shows what command is being executed when running a test. This is how it looks like for me:
xdc.exe XDCOPTIONS=v test
#
# running prog.x64P ...
'E:/XDCtools Installs/xdctools_3_21_00_55/packages/ti/platforms/sim64Pxx/Windows
/kelvin' -quiet -mem_ignore 'C:\rtsc\examples\lesson5\prog.x64P'
Hello World


I see you are building for two targets. My guess is that the error comes from 64P and not from Mingw. The error message you are getting indicates that the command line generated to run the program is invalid.
There is another way to find out that command line. Look into the directory package/cfg in your lesson5 directory. You should see one or two files with the extension .dep. Open these files and find the line that starts with
'define EXEC.prog.x64P' or 'define EXEC.prog.x86GW'.
Please post what's between that line and the line
'endef'
in all .dep files you have.
Re: Problem with RTSC module primer lesson 5 [message #670332 is a reply to message #667605] Fri, 13 May 2011 14:32 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
Sasha,

This is what I get when executing the commands you said:

D:\examples\lesson5>xdc clean

D:\examples\lesson5>xdc XDCOPTIONS=v test
#
# making package.mak (because of package.bld) ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/xs  -Dxdc.path="C:/PROGRA~2/TEXASI~1/xd
ctools_3_20_03_63/packages;.." -Dxdc.root=C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_
63 -Dxdc.hostOS=Windows -Dconfig.importPath=".;C:/PROGRA~2/TEXASI~1/xdctools_3_2
0_03_63/packages;..;C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63;C:/PROGRA~2/TEXASI~
1/xdctools_3_20_03_63/etc" -Dxdc.bld.targets="" -DTOOLS=   -f C:/PROGRA~2/TEXASI
~1/xdctools_3_20_03_63/packages/xdc/bld/bld.js ../config.bld package.bld package
.mak
#
# generating interfaces for package lesson5 (because package/package.xdc.inc is
older than package.xdc) ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/xs -Dxdc.path="C:/PROGRA~2/TEXASI~1/xdc
tools_3_20_03_63/packages;.." -Dxdc.root=C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_6
3 -Dxdc.hostOS=Windows -Dconfig.importPath=".;C:/PROGRA~2/TEXASI~1/xdctools_3_20
_03_63/packages;..;C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63;C:/PROGRA~2/TEXASI~1
/xdctools_3_20_03_63/etc" -Dxdc.bld.targets="" -DTOOLS=  -f xdc/services/intern/
cmd/build.xs  -m package/package.xdc.dep -i package/package.xdc.inc package.xdc
#
# configuring prog.x64P from package/cfg/prog_x64P.cfg ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/xs -Dxdc.path="C:/PROGRA~2/TEXASI~1/xdc
tools_3_20_03_63/packages;.." -Dxdc.root=C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_6
3 -Dxdc.hostOS=Windows -Dconfig.importPath=".;C:/PROGRA~2/TEXASI~1/xdctools_3_20
_03_63/packages;..;C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63;C:/PROGRA~2/TEXASI~1
/xdctools_3_20_03_63/etc" -Dxdc.bld.targets="" -DTOOLS=   xdc.cfg prog.x64P pack
age/cfg/prog_x64P.cfg package/cfg/prog_x64P
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg/prog/prog.o64P
#
# cl64P prog.c ...
C:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/bin/cl6x -c  -qq -pdsw225 -mv64p
 -eo.o64P -ea.s64P   -Dxdc_cfg__header__='lesson5/package/cfg/prog_x64P.h'  -Dxd
c_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_bld__profile_re
lease -Dxdc_bld__vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~1/xdctools_3_20_03
_63/packages -I.. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/include -fs=
./package/cfg/prog -fr=./package/cfg/prog -fc prog.c
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/mkdep -a package/cfg/prog/prog.o64P
.dep -p package/cfg/prog -s o64P prog.c -C   -qq -pdsw225 -mv64p -eo.o64P -ea.s6
4P   -Dxdc_cfg__header__='lesson5/package/cfg/prog_x64P.h'  -Dxdc_target_name__=
C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_bld__profile_release -Dxdc_bld_
_vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/packages -I.
. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/include -fs=./package/cfg/pr
og -fr=./package/cfg/prog
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg/prog_x64P.o64P
#
# cl64P package/cfg/prog_x64P.c ...
C:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/bin/cl6x -c  -qq -pdsw225 -mo --
no_compress -mv64p -eo.o64P -ea.s64P   -Dxdc_cfg__header__='lesson5/package/cfg/
prog_x64P.h'  -Dxdc_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dx
dc_bld__profile_release -Dxdc_bld__vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~
1/xdctools_3_20_03_63/packages -I.. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/
c6000/include -fs=./package/cfg -fr=./package/cfg -fc package/cfg/prog_x64P.c
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/mkdep -a package/cfg/prog_x64P.o64P
.dep -p package/cfg -s o64P package/cfg/prog_x64P.c -C   -qq -pdsw225 -mo --no_c
ompress -mv64p -eo.o64P -ea.s64P   -Dxdc_cfg__header__='lesson5/package/cfg/prog
_x64P.h'  -Dxdc_target_name__=C64P -Dxdc_target_types__=ti/targets/std.h -Dxdc_b
ld__profile_release -Dxdc_bld__vers_1_0_7_0_3 -O2  -I. -IC:/PROGRA~2/TEXASI~1/xd
ctools_3_20_03_63/packages -I.. -IC:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c600
0/include -fs=./package/cfg -fr=./package/cfg
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f prog.x64P
#
# lnk64P prog.x64P ...
C:/PROGRA~2/TEXASI~1/xdctools_3_20_03_63/bin/rm -f package/cfg//prog.x64P.map
C:/PROGRA~2/TEXASI~1/ccsv4/tools/compiler/c6000/bin/lnk6x -w -q -u _c_int00  -q
-o prog.x64P package/cfg/prog/prog.o64P package/cfg/prog_x64P.o64P  package/cfg/
prog_x64P.xdl  -c -m package/cfg//prog.x64P.map -l C:/PROGRA~2/TEXASI~1/ccsv4/to
ols/compiler/c6000/lib/rts64plus.lib
C:/Users/SEBAST~1/AppData/Local/Temp/make4640-1.sh: 1: Syntax error: "(" unexpec
ted
gmake.exe: *** [prog.x64P.test] Error 2


There is a file called "prog_x64P.dep". This is the fragment you wanted:

define EXEC.prog.x64P

C:/Program Files (x86)/Texas Instruments/xdctools_3_20_03_63/packages/ti/platforms/sim64Pxx/Windows/kelvin -quiet -mem_ignore D:\examples\lesson5\prog.x64P
endef


If I run "xdc all", I get a 2nd .dep file called "prog_x86GW.dep". This is the relevant fragment:

define EXEC.prog.x86GW

./prog.x86GW
endef


Thanks for your help.
Re: Problem with RTSC module primer lesson 5 [message #671137 is a reply to message #666709] Mon, 16 May 2011 21:00 Go to previous messageGo to next message
Sasha Slijepcevic is currently offline Sasha SlijepcevicFriend
Messages: 90
Registered: July 2009
Member
That seems to be an instance of this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=282605

The fix is available in 3.22. If you can update to that release, that would be the cleanest way to solve the problem.
Since the fix is quite basic, you can also make that change in your current installation and see if that helps. Here is the fix from <XDCtools>/packages/ti/platforms/sim64Pxx/Platform.xs
106,107c106,107
<         command = packagePath + os + "/kelvin -quiet -mem_ignore "
<             + java.io.File(prog.name).getAbsolutePath();
---
>         command = "'" + packagePath + os + "/kelvin' -quiet -mem_ignore '"
>             + java.io.File(prog.name).getAbsolutePath() + "'";
Re: Problem with RTSC module primer lesson 5 [message #684947 is a reply to message #671137] Thu, 16 June 2011 14:04 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
I updated xdctools to 3.22, and modified common.mak accordingly, but it didn't make a difference (I used xdc clean before trying to run the example again). Also, the bug you mention doesn't really look like what is happening to me. In addition, I tried this in another PC and it worked using the same setup. The only difference I notice between the PCs is that mine uses windows 7 x64, whereas the other uses the 32-bit version.

Other than that, I have been able to run even SYS/BIOS successfully. Please help me, I am starting a very important project for me and I would really like to do it using RTSC, but this problem kind of discourages me. Thanks in advance.
Re: Problem with RTSC module primer lesson 5 [message #685176 is a reply to message #684947] Fri, 17 June 2011 01:09 Go to previous messageGo to next message
Sasha Slijepcevic is currently offline Sasha SlijepcevicFriend
Messages: 90
Registered: July 2009
Member
In your email where you posted the content of the file prog_x64.dep, you can see that there are no quotes surrounding the path to the executable 'kelvin'. Is the content of that file same on both PCs you were using?
If you run
xdc XDCOPTIONS=v test

on the 32-bit PC, what's the output? You don't have to post everything, only the output after the linker command line.
Re: Problem with RTSC module primer lesson 5 [message #707353 is a reply to message #685176] Mon, 01 August 2011 14:44 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
Sorry for taking too long, I've been a little busy.

I recently upgraded to xdctools 3.22.01.21, and I am still having the same problem. I do not have access to the 32-bit computer anymore, so I used instead my own Windows 7's XP-mode virtual PC. It turns out that lesson 5 runs successfully in XP mode (at least for p64P target).

File "prog_p64P.dep" in both cases have the following lines:

Windows 7 64-bit
define EXEC.prog.x64P

'C:/Program Files (x86)/Texas Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin' -quiet -mem_ignore 'D:\examples\lesson5\prog.x64P'
endef


XP-Mode
define EXEC.prog.x64P

'C:/Program Files/Texas Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin' -quiet -mem_ignore 'C:\examples\lesson5\prog.x64P'
endef


It seems to me that xdc (or whatever is executed in the background) cannot process "(" or ")" in a filename. And since the default path in a x64 PC for non-64-bit applications is "Program Files (x86)", this problem only occurs in my 64-bit Windows 7. I hope you can correct this issue in a future release, and if you have a quick solution, please let me know.

I have another problem. Now lesson 1 does not run. Everything seems fine when I run "gmake all", but when I run "gmake test", the following appears:
C:/Progra~2/TexasI~1/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
Cannot find 'C:/Program along the path [D:\examples\lesson1\., C:\Progra~2\Texas
I~1\xdctools_3_22_01_21, C:\Program Files (x86)\Texas Instruments\xdctools_3_22_
01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin, C:\watcom-1.3\binnt,
 C:\watcom-1.3\binw, C:\Program Files\Common Files\Microsoft Shared\Windows Live
, C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live, C:\Program
Files (x86)\ATI Stream\bin\x86_64, C:\Program Files (x86)\ATI Stream\bin\x86, C:
\Windows\system32, C:\Windows, C:\Windows\System32\Wbem, C:\Windows\System32\Win
dowsPowerShell\v1.0, C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static
, C:\Program Files (x86)\Windows Live\Shared, C:\Program Files (x86)\Microchip\M
PLAB C32 Suite\bin, C:\Program Files\MATLAB\R2010b\runtime\win64, C:\Program Fil
es\MATLAB\R2010b\bin, C:\Program Files (x86)\Common Files\Acronis\SnapAPI, C:\Pr
ogram Files (x86)\Microsoft SQL Server\100\Tools\Binn, C:\Program Files\Microsof
t SQL Server\100\Tools\Binn, C:\Program Files\Microsoft SQL Server\100\DTS\Binn,
 C:\Program Files\Microsoft Windows Performance Toolkit, C:\Program Files (x86)\
Texas Instruments\xdctools_3_22_01_21]

It looks like an issue with the space in the "Program Files" name. I tried changing the pathnames in "common.mak" and "config.bld" for their 8.3 versions, and still got the same result. It looks like a bug with the 3.22.01 version, since the correct result is shown if I run:
D:\examples\lesson1>C:/Progra~2/TexasI~1/xdctools_3_20_08_88/xs xdc.tools.loader
 prog.out
Hello World

The behavior is the same in the XP-mode PC. What can I do?

Thanks in advance for your help.
Re: Problem with RTSC module primer lesson 5 [message #708580 is a reply to message #707353] Wed, 03 August 2011 00:20 Go to previous messageGo to next message
Dave Russo is currently offline Dave RussoFriend
Messages: 172
Registered: July 2009
Senior Member
As you guessed, spaces and '()' characters in files names cause quite a
problem for GNU make (the underlying tool used by xdc).

In some cases we are convert these files to 8.3 names, in other cases we
are able to quote the spaces but, in the end, problems are always
possible because at it's core GNU make simply does not support file
names with special characters in them.

The best answer is to install XDCtools in a directory _without_ spaces
or '()' characters. If this is not possible, you may be able to
"manually" override offending paths with their 8.3 equivalents.

For example, in your example below, you can get the 8.3 equivalent name
for "C:/Program Files (x86)/Texas
Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin"
and use this to define the command used to run the test via
Program.execCmd; see
http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/cfg/Program.html#exec.Cmd.

For what it's worth, running xdc with XDCOPTIONS=v often help diagnose
these problems; xdc will display _exactly_ what it's trying to execute.
xdc XDCOPTIONS=v ...

On 8/1/2011 7:44 AM, linkinsebas wrote:
> Sorry for taking too long, I've been a little busy.
>
> I recently upgraded to xdctools 3.22.01.21, and I am still having the
> same problem. I do not have access to the 32-bit computer anymore, so I
> used instead my own Windows 7's XP-mode virtual PC. It turns out that
> lesson 5 runs successfully in XP mode (at least for p64P target).
> File "prog_p64P.dep" in both cases have the following lines:
>
> Windows 7 64-bit
> define EXEC.prog.x64P
>
> 'C:/Program Files (x86)/Texas
> Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin'
> -quiet -mem_ignore 'D:\examples\lesson5\prog.x64P'
> endef
>
> XP-Mode
>
> define EXEC.prog.x64P
>
> 'C:/Program Files/Texas
> Instruments/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/kelvin'
> -quiet -mem_ignore 'C:\examples\lesson5\prog.x64P'
> endef
>
> It seems to me that xdc (or whatever is executed in the background)
> cannot process "(" or ")" in a filename. And since the default path in a
> x64 PC for non-64-bit applications is "Program Files (x86)", this
> problem only occurs in my 64-bit Windows 7. I hope you can correct this
> issue in a future release, and if you have a quick solution, please let
> me know.
>
> I have another problem. Now lesson 1 does not run. Everything seems fine
> when I run "gmake all", but when I run "gmake test", the following appears:
> C:/Progra~2/TexasI~1/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
> Cannot find 'C:/Program along the path [D:\examples\lesson1\.,
> C:\Progra~2\Texas
> I~1\xdctools_3_22_01_21, C:\Program Files (x86)\Texas
> Instruments\xdctools_3_22_
> 01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin,
> C:\watcom-1.3\binnt,
> C:\watcom-1.3\binw, C:\Program Files\Common Files\Microsoft
> Shared\Windows Live
> , C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live,
> C:\Program
> Files (x86)\ATI Stream\bin\x86_64, C:\Program Files (x86)\ATI
> Stream\bin\x86, C:
> \Windows\system32, C:\Windows, C:\Windows\System32\Wbem,
> C:\Windows\System32\Win
> dowsPowerShell\v1.0, C:\Program Files (x86)\ATI
> Technologies\ATI.ACE\Core-Static
> , C:\Program Files (x86)\Windows Live\Shared, C:\Program Files
> (x86)\Microchip\M
> PLAB C32 Suite\bin, C:\Program Files\MATLAB\R2010b\runtime\win64,
> C:\Program Fil
> es\MATLAB\R2010b\bin, C:\Program Files (x86)\Common
> Files\Acronis\SnapAPI, C:\Pr
> ogram Files (x86)\Microsoft SQL Server\100\Tools\Binn, C:\Program
> Files\Microsof
> t SQL Server\100\Tools\Binn, C:\Program Files\Microsoft SQL
> Server\100\DTS\Binn,
> C:\Program Files\Microsoft Windows Performance Toolkit, C:\Program Files
> (x86)\
> Texas Instruments\xdctools_3_22_01_21]
> It looks like an issue with the space in the "Program Files" name. I
> tried changing the pathnames in "common.mak" and "config.bld" for their
> 8.3 versions, and still got the same result. It looks like a bug with
> the 3.22.01 version, since the correct result is shown if I run:
> D:\examples\lesson1>C:/Progra~2/TexasI~1/xdctools_3_20_08_88/xs
> xdc.tools.loader
> prog.out
> Hello World
> The behavior is the same in the XP-mode PC. What can I do?
>
> Thanks in advance for your help.
Re: Problem with RTSC module primer lesson 5 [message #714964 is a reply to message #708580] Thu, 11 August 2011 22:34 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
I have reinstalled all to C:\TI, so the new path to xdctools is C:/TI/xdctools_3_22_01_21. Lesson 5 seems to work now for target 64P:
D:\examples\lesson5>xdc all
making package.mak (because of package.bld) ...
gnu.targets.Mingw: warning: exec of 'C:/MinGW/mingw32/bin/ld -v' failed:; check
tools installation
gnu.targets.Mingw: warning: can't determine binutils version;
Check if C:/MinGW/bin/ld can run on
Windows.
Also, try explicitly setting the BINVERS configuration parameter.
generating interfaces for package lesson5 (because package/package.xdc.inc is ol
der than package.xdc) ...
configuring prog.p64P from package/cfg/prog_p64P.cfg ...
cl64P package/cfg/prog_p64P.c ...
configuring prog.p86GW from package/cfg/prog_p86GW.cfg ...
cl86GW package/cfg/prog_p86GW.c ...
cl64P prog.c ...
lnk64P prog.x64P ...
cl86GW prog.c ...
lnk86GW prog.x86GW ...
all files complete.

D:\examples\lesson5>xdc test,64P
running prog.x64P ...
Hello World


However, target 86GW still has problems:
D:\examples\lesson5>xdc test,86GW
running prog.x86GW ...

A window appears here saying that "The program can't start because libstdc++-6.dll is missing from your computer. Try reinstalling the program to fix this problem.". After I close the window, the following additional output appears:
gmake.exe[1]: *** [prog.x86GW.test] Error -1073741515
xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2


In addition, lesson 1 still does not work.

D:\examples\lesson1>gmake all
C:/TI/xdctools_3_22_01_21/xs xdc.tools.configuro -c C:/TI/ccsv4/tools/compiler/c
6000 -t ti.targets.C64P -p ti.platforms.sim64Pxx -o cfgsite prog.cfg
making package.mak (because of package.bld) ...
generating interfaces for package cfgsite (because package/package.xdc.inc is ol
der than package.xdc) ...
configuring prog.p64P from package/cfg/prog_p64P.cfg ...
cl64P package/cfg/prog_p64P.c ...
C:/TI/ccsv4/tools/compiler/c6000/bin/cl6x -q -@cfgsite/compiler.opt -c prog.c
C:/TI/ccsv4/tools/compiler/c6000/bin/cl6x -q -z -c prog.obj cfgsite/linker.cmd -
o prog.out -l C:/TI/ccsv4/tools/compiler/c6000/lib/rts64plus.lib

D:\examples\lesson1>gmake test
C:/TI/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
Cannot find 'C:/TI/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/ke
lvin' along the path [D:\examples\lesson1\., C:\TI\xdctools_3_22_01_21, C:\TI\xd
ctools_3_22_01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin, C:\watco
m-1.3\binnt, C:\watcom-1.3\binw, C:\Program Files\Common Files\Microsoft Shared\
Windows Live, C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live,
 C:\Program Files (x86)\ATI Stream\bin\x86_64, C:\Program Files (x86)\ATI Stream
\bin\x86, C:\Windows\system32, C:\Windows, C:\Windows\System32\Wbem, C:\Windows\
System32\WindowsPowerShell\v1.0, C:\Program Files (x86)\ATI Technologies\ATI.ACE
\Core-Static, C:\Program Files (x86)\Windows Live\Shared, C:\Program Files (x86)
\Microchip\MPLAB C32 Suite\bin, C:\Program Files\MATLAB\R2010b\runtime\win64, C:
\Program Files\MATLAB\R2010b\bin, C:\Program Files (x86)\Common Files\Acronis\Sn
apAPI, C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn, C:\Program Fi
les\Microsoft SQL Server\100\Tools\Binn, C:\Program Files\Microsoft SQL Server\1
00\DTS\Binn, C:\Program Files\Microsoft Windows Performance Toolkit, C:\TI\xdcto
ols_3_22_01_21]
D:\examples\lesson1>


File C:\TI\xdctools_3_22_01_21\packages\ti\platforms\sim64Pxx\Windows\kelvin DOES exist, I can even run it manually and it works:
D:\examples\lesson1>C:\TI\xdctools_3_22_01_21\packages\ti\platforms\sim64Pxx\Win
dows\kelvin prog.out
20110811-17:25:27: C:\TI\xdctools_3_22_01_21\packages\ti\platforms\sim64Pxx\Wind
ows\kelvin prog.out
simulating Joule ISA
Hello World
Simulation done:
(lots of numbers and statistics...)


This has nothing to do with spaces in pathnames, since I am not using them anymore, and because 'gmake test' works perfectly fine with version 3.20.08.88 even when I use xdctools in "C:/Program Files/Texas Instruments.....", so this looks like a bug that should be fixed.

Finally, a suggestion: if spaces in pathnames give so much trouble, xdctools should not have as the default installation path one that has spaces in it.

Well, in summary: lesson1 is now giving trouble, and the original problem with lesson5 was "solved" for target 64P, but I could still use some help for target 86GW. Any help will be appreciated. Thanks in advance.
Re: Problem with RTSC module primer lesson 5 [message #714972 is a reply to message #714964] Thu, 11 August 2011 23:10 Go to previous messageGo to next message
Dave Russo is currently offline Dave RussoFriend
Messages: 172
Registered: July 2009
Senior Member
On 8/11/2011 3:34 PM, linkinsebas wrote:
> I have reinstalled all to C:\TI, so the new path to xdctools is
> C:/TI/xdctools_3_22_01_21. Lesson 5 seems to work now for target 64P:
>
>
Excellent!

>
>
> However, target 86GW still has problems:
> D:\examples\lesson5>xdc test,86GW
> running prog.x86GW ...
> A window appears here saying that "The program can't start because
> libstdc++-6.dll is missing from your computer. Try reinstalling the
> program to fix this problem.". After I close the window, the following
> additional output appears:
> gmake.exe: *** [prog.x86GW.test] Error -1073741515
> xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2
>
Hummmm. This looks like a mingw installation/path issue.
libstdc++-6.dll looks like a mingw dll that gcc is trying to use. If
this DLL is not in the installation you may have to use the
"-static-libstdc++" switch for the linker to avoid this message.

> In addition, lesson 1 still does not work.
> D:\examples\lesson1>gmake test
> C:/TI/xdctools_3_22_01_21/xs xdc.tools.loader prog.out
> Cannot find
> 'C:/TI/xdctools_3_22_01_21/packages/ti/platforms/sim64Pxx/Windows/ke
> lvin' along the path [D:\examples\lesson1\., C:\TI\xdctools_3_22_01_21,
> C:\TI\xd
> ctools_3_22_01_21, C:\Program Files (x86)\Microchip\mplabc30\v3.25\bin,

This is a bug in the sim64Pxx platform package on Windows.

>
> Finally, a suggestion: if spaces in pathnames give so much trouble,
> xdctools should not have as the default installation path one that has
> spaces in it.
>
We were forced to make the default installation the "Windows standard"
which is quite unfriendly to programmers accustomed to make-based
command line tools.

> Well, in summary: lesson1 is now giving trouble, and the original
> problem with lesson5 was "solved" for target 64P, but I could still use
> some help for target 86GW. Any help will be appreciated. Thanks in advance.
Re: Problem with RTSC module primer lesson 5 [message #714996 is a reply to message #714972] Fri, 12 August 2011 02:50 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
Dave:

Where do I have to put this "-static-libstdc++"?
I discovered that the solicited files are in "C:\MinGW\bin" and "C:\MinGW\mingw32\bin", so I tried adding them to the path, and at least "xdc all" does not display any error message:
D:\examples\lesson5>xdc all
making package.mak (because of package.bld) ...
generating interfaces for package lesson5 (because package/package.xdc.inc is ol
der than package.xdc) ...
configuring prog.p64P from package/cfg/prog_p64P.cfg ...
cl64P package/cfg/prog_p64P.c ...
configuring prog.p86GW from package/cfg/prog_p86GW.cfg ...
cl86GW package/cfg/prog_p86GW.c ...
cl64P prog.c ...
lnk64P prog.x64P ...
cl86GW prog.c ...
lnk86GW prog.x86GW ...
all files complete.

However, "xdc test" still does not work:
D:\examples\lesson5>xdc test,86GW
running prog.x86GW ...
process_begin: CreateProcess(D:\examples\lesson5\prog.x86GW, ./prog.x86GW, ...)
failed.
make (e=193): Error 193
gmake.exe[1]: *** [prog.x86GW.test] Error 193
xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2


As for the bug with sim64Pxx, do you have any idea about when it will get fixed? Is there something I can do in the meantime?

Thanks for your help!
Re: Problem with RTSC module primer lesson 5 [message #715173 is a reply to message #714996] Fri, 12 August 2011 14:56 Go to previous messageGo to next message
Dave Russo is currently offline Dave RussoFriend
Messages: 172
Registered: July 2009
Senior Member
On 8/11/2011 7:50 PM, linkinsebas wrote:
> Where do I have to put this "-static-libstdc++"?
> I discovered that the solicited files are in "C:\MinGW\bin" and
> "C:\MinGW\mingw32\bin", so I tried adding them to the path, and at least
> "xdc all" does not display any error message:

In this case, you don't need to add "-static-libstdc++". Using this
option causes the mingw compiler to statically link in the C standard
library (which makes your executable bigger) but also has the effect of
avoiding the need to load the "missing" DLLs.

> However, "xdc test" still does not work:
> D:\examples\lesson5>xdc test,86GW
> running prog.x86GW ...
> process_begin: CreateProcess(D:\examples\lesson5\prog.x86GW,
> ./prog.x86GW, ...)
> failed.
> make (e=193): Error 193
> gmake.exe[1]: *** [prog.x86GW.test] Error 193
> xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2
>
Hummm. Are you able to run prog.x86GW directly from the command line?
If so, the problem is in how the generated makefile is running the
executable. If not, there is a problem in the build of the executable.

Can you post the output when you run "xdc XDCOPTIONS=v test,86GW"? This
will display _exactly_ what the makefile is running.

> As for the bug with sim64Pxx, do you have any idea about when it will
> get fixed? Is there something I can do in the meantime?

Yes. Sasha is looking at the issue now and will post a patch to the
platform. It looks like a "simple" (but subtle) quoting problem when
the platform constructs the command to run.

If you're feeling adventurous, take a look at the file
ti/platforms/sim64Pxx/Platform.xs. The following line constructs the
command line used to run the executable.

command = "'" + packagePath + os + "/kelvin' -quiet -mem_ignore '"
+ java.io.File(prog.name).getAbsolutePath() + "'";

This probably needs to be changed to eliminate the "'" characters
surrounding the command. Something like the following _might_ work:

command = packagePath + os + "/kelvin -quiet -mem_ignore '"
+ java.io.File(prog.name).getAbsolutePath() + "'";
Re: Problem with RTSC module primer lesson 5 [message #715195 is a reply to message #715173] Fri, 12 August 2011 17:11 Go to previous messageGo to next message
Sasha Slijepcevic is currently offline Sasha SlijepcevicFriend
Messages: 90
Registered: July 2009
Member
Quote:

> As for the bug with sim64Pxx, do you have any idea about when it will
> get fixed? Is there something I can do in the meantime?

Yes. Sasha is looking at the issue now and will post a patch to the
platform. It looks like a "simple" (but subtle) quoting problem when
the platform constructs the command to run.

If you're feeling adventurous, take a look at the file
ti/platforms/sim64Pxx/Platform.xs. The following line constructs the
command line used to run the executable.

command = "'" + packagePath + os + "/kelvin' -quiet -mem_ignore '"
+ java.io.File(prog.name).getAbsolutePath() + "'";

This probably needs to be changed to eliminate the "'" characters
surrounding the command. Something like the following _might_ work:

command = packagePath + os + "/kelvin -quiet -mem_ignore '"
+ java.io.File(prog.name).getAbsolutePath() + "'";


Yes, I am looking at the problem, and I am trying to find a solution that would work for both cases, lesson1 and lesson5 even if there are spaces in the paths. But, since you installed XDCtools in a directory without spaces, the following should work for you:
command = packagePath + os + "/kelvin -quiet -mem_ignore \""
+ java.io.File(prog.name).getAbsolutePath() + "\"";

Re: Problem with RTSC module primer lesson 5 [message #715284 is a reply to message #715195] Sat, 13 August 2011 04:19 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
Sasha and Dave, your correction worked perfectly for lesson 1. Thanks!

Here is the output for lesson5 target x86GW when using XDCOPTIONS=v:
D:\examples\lesson5>xdc test,86GW XDCOPTIONS=v
#
# running prog.x86GW ...
./prog.x86GW
process_begin: CreateProcess(D:\examples\lesson5\prog.x86GW, ./prog.x86GW, ...)
failed.
make (e=193): Error 193
gmake.exe[1]: *** [prog.x86GW.test] Error 193
xdctools_3_22_01_21\gmake.exe: *** [prog.x86GW.test] Error 2

Not much of a difference I think...

How do I run prog.x86GW directly from the command line? Remember that I am in Windows, I am supossed to be able to run only .exe's directly.

Thanks for your help!
Re: Problem with RTSC module primer lesson 5 [message #715930 is a reply to message #715284] Tue, 16 August 2011 02:38 Go to previous messageGo to next message
Sasha Slijepcevic is currently offline Sasha SlijepcevicFriend
Messages: 90
Registered: July 2009
Member
The problem with lesson5 is caused by a mismatch between the content of the linker command script package/cfg/prog_p86GW.xdl and the option -T passed for it.
The linker command line for MinGW in XDCtools 3.22.01 is:
D:/MinGW/bin/mingw32-gcc.exe -Wl,--gc-sections -o prog.x86GW package/cfg/prog_p86GW.o86GW package/cfg/prog/prog.o86GW -Wl,-T,package/cfg/prog_p86GW.xdl  -Wl,-Map=package/cfg//prog.x86GW.map -lstdc++ -LD:/MinGW/lib

The option -T should not preceed that file, and the correct command line is:
D:/MinGW/bin/mingw32-gcc.exe -Wl,--gc-sections -o prog.x86GW package/cfg/prog_p86GW.o86GW package/cfg/prog/prog.o86GW package/cfg/prog_p86GW.xdl  -Wl,-Map=package/cfg//prog.x86GW.map -lstdc++ -LD:/MinGW/lib


The workaround requires editing a file ITarget.xs, in xdctools_3_22_01_21/packages/gnu/targets. The line 90
    if (target.BINVERS >= "2.19") {

should be replaced with
    if (target.BINVERS >= "2.19" && target.$name != "gnu.targets.Mingw") {


Once you fix that, you'll be able to run from the command line by simply typing
prog.x86GW

[Updated on: Tue, 16 August 2011 02:39]

Report message to a moderator

Re: Problem with RTSC module primer lesson 5 [message #717167 is a reply to message #715930] Fri, 19 August 2011 14:01 Go to previous messageGo to next message
linkinsebas is currently offline linkinsebasFriend
Messages: 22
Registered: April 2011
Junior Member
With this last workaround, the examples are now working perfectly fine. Thanks!

Just a last couple of questions: Are these corrections going to be integrated in a future release? Will xdctools properly support spaces and parenthesis in pathnames in a future release?

Thank you Sasha and Dave.
Re: Problem with RTSC module primer lesson 5 [message #717308 is a reply to message #717167] Fri, 19 August 2011 22:35 Go to previous message
Sasha Slijepcevic is currently offline Sasha SlijepcevicFriend
Messages: 90
Registered: July 2009
Member
Yes, they will be in the first post-3.22 release for sure, and I'll see if I can add them to the next 3.22 patch.
Previous Topic:java.lang.OutOfMemoryError: Java heap space -- help
Next Topic:dash in package name
Goto Forum:
  


Current Time: Thu Nov 27 18:41:08 GMT 2014

Powered by FUDForum. Page generated in 0.02382 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software