Alex,
It looks like, based on your cut and paste below, /bin/sh is objecting to "-p" (i.e. lowercase p). The XDC option that we use in the workshop is a capital P (as you indicate later in the message), and the flags are cases sensitive. I am also concerned that you are getting the error returned from /bin/sh. The way xdc usually works is that any unrecognized command line option is passed to gmake, and if gmake doesn't recognize the command line option, it returns an error. Lowercase p is actually a flag in gmake (print database) that prints out a whole lot of stuff if invoked, so even when I run xdc with lowercase p I don't get an error returned. Are you using the runxdc.sh script at the top level of each lab directory? This script should invoke the tool properly, assuming setpaths.sh is set correctly. The reason that you are getting the error that you do when no "-P" option is used is probably because you are running from the top level of the lab directory (which is what the lab instructions tell you to do). This is the right place to run from if you use the P option because xdc will descend into each package directory. However, if you run xdc without -P, it looks for package.xdc in the current directory. So if you wanted to run xdc without -P, you would need to first change into the app directory and then run the tool. If you run: # xdc -h You can get a printout of xdc's command line options. The trick we use in the workshop is that we build all of the packages in a given lab exercise by specifying # xdc -P * At the top level of the lab directory. In the early labs there is only one package to build, but in later labs this trick is a quick way to build all packages in the lab directory. Note that a better way would be to use # xdc -PR Which recursively builds all packages in the current directory, but at the time that the lab exercises were put together, that option did not work correctly. The issue has since been fixed. If none of this explanation helps (quite possible), then can you please modify the runxdc.sh file so that the top instruction reads: #! /bin/sh --verbose This puts the shell in verbose mode so that it will echo all commands that the script sends to the shell. If you could do this and capture the output when you run the script - most importantly the line that invokes the xdc tool - and send it back to me, I will take a look and try and figure out what is causing the problem. Regards, Steve Preissig Texas Instruments Technical Training Organization 9260 Waits Ferry Crossing Duluth, GA 30097 [EMAIL PROTECTED] (770) 840-0783 I'm just starting out developing on the DVEVM and I've been on the TI developers course for the DVEVM. I brought back with me all of the workshop files etc that I was using on the course and when I got home and bought my board I tried out again the workshop files. I've tried compiling just as I did on the course but when I try and compile using xdc I get the following error: Making all: Tue Nov 6 15:17:09 GMT 2007... ========= .interfaces [app/] ====== making package.mak (because of package.bld) ... /bin/sh: Illegal option -p gmake[1]: *** [package.mak] Error 2 gmake: *** [app/,.interfaces] Error 2 If I run xdc without the -P option (xdc "CE_INSTALL_DIR/packages" $(pwd)"/../config.bld") I get the following error: /home/alex/dvevm_1_10/xdctools_1_21/bin/xdcdir: error : Can't open ./package.xdc /home/alex/dvevm_1_10/xdctools_1_21/packages/xdc/bld/xdc_rules.mak:319: *** Can't find the package build script package.bld. Stop. How do I make sure that xdc can find the package.xdc file?? Its driving me nuts! Thanks, Alex
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
