Are you using CE 1.10 or 1.20? The first bit of your email says you're moving to CE 1.20... but the autogenerated .xdl file is showing that you're still using CE 1.10 (or at least the XDCPATH was pointing at CE 1.10 when the config step was run). Also, which version of XDC Tools are you using? If you're using CE 1.20, you need to be using XDC Tools 2.95.01 or later. Chris
________________________________
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
com] On Behalf Of Kim Klaiman
Sent: Friday, December 28, 2007 12:18 PM
To: davinci-linux-open-source@linux.davincidsp.com
Subject: Moving from MV kernel to TI kernel
Hello,
Due to few issues on MV kernel, we have decided to move (at
least for now) to TI kernel.
We have a CE application which is integrated into our main
program.
Everything worked fine when compiled with MV kernel and CE 1.10.
However, when moving to TI kernel and CE 1.20, the linker gives the
following messages:
arm_v5t_le-gcc: this: No such file or directory
arm_v5t_le-gcc: file: No such file or directory
arm_v5t_le-gcc: was: No such file or directory
arm_v5t_le-gcc: generated: No such file or directory
arm_v5t_le-gcc: by: No such file or directory
arm_v5t_le-gcc: linkcmd.xdt: No such file or directory
arm_v5t_le-gcc: from: No such file or directory
arm_v5t_le-gcc: the: No such file or directory
arm_v5t_le-gcc: gnu.targets: No such file or directory
arm_v5t_le-gcc: package: No such file or directory
arm_v5t_le-gcc: INPUT(: No such file or directory
arm_v5t_le-gcc: ): No such file or directory
After doing some investigation, I found out that pkg_x470MV.xdl
looks like this:
/* this file was generated by linkcmd.xdt from the gnu.targets
package */
INPUT(
/home/dvevm1/dvevm_1_20/codec_engine_1_10_01/packages/ti/sdo/ce/bioslog/
lib/bioslog.a470MV
/home/dvevm1/dvevm_1_20/codec_engine_1_10_01/packages/ti/sdo/ce/audio/li
b/debug/audio.a470MV
.....
/home/dvevm1/dvevm_1_20/cmem_1_02/packages/ti/sdo/linuxutils/cmem/lib/cm
emd.a
)
In MV kernel, it looks like this:
/home/dvevm1/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/audio/lib/a
udio_debug.a470MV
/home/dvevm1/dvevm_1_10/codec_engine_1_02/packages/ti/sdo/ce/speech/lib/
speech_debug.a470MV
....
/home/dvevm1/dvevm_1_10/cmem_1_01/packages/ti/sdo/linuxutils/cmem/lib/cm
emd.a
So I guess that in TI kernel, the first two and the last lines
are causing the linker to fail.
How can I fix this problem?
Kim Klaiman
Senior Embedded Software Engineer
Bioscrypt Inc.
T 905.940.7756
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
www.bioscrypt.com <http://www.bioscrypt.com/>
Leading provider of enterprise access control solutions
<<image001.gif>>
_______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
