The libtool version I used is 1.2517, and it is just as you said that the path is caused by other dependent .la file,thank you!
Hello Volter,
* Volter Yen wrote on Wed, Nov 14, 2007 at 03:12:18AM CET:
>
> $/bin/sh ../libtool --tag=CC --mode=link arm_v5t_le-gcc -g -O2 -L/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib -o libgstflumpegdemux.la -rpath /home/test/workdir/filesys/usr/lib/gstreamer-0.10 -module -avoid-version -export-symbols-regex _*\(gst_\|Gst\|GST_\).* libgstflumpegdemux_la-flumpegdemux.lo libgstflumpegdemux_la-gstmpegdesc.lo libgstflumpegdemux_la-gstmpegdemux.lo libgstflumpegdemux_la-gstpesfilter.lo libgstflumpegdemux_la-gstmpegtsdemux.lo libgstflumpegdemux_la-flutspatinfo.lo libgstflumpegdemux_la-flutspmtinfo.lo libgstflumpegdemux_la-flutspmtstreaminfo.lo libgstflumpegdemux_la-gstsectionfilter.lo -pthread -L/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -ldl -lgthread-2.0 -lxml2 -lpthread -lz -lm -lglib-2.0 -pthread -L/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target/usr/lib -lgstbase-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -ldl -lgthread-2.0 -lxml2 -lpthread -lz -lm -lglib-2.0
>
> outputing on the screen....
> $grep: /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/usr/lib/libglib-2.0.la: No such file or directory
> /bin/sed: can't read /opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/usr/lib/libglib-2.0.la: No such file or directory
> libtool: link: `/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/usr/lib/libglib-2.0.la' is not a valid libtool archive
Which `../ 1.2517 --version' is this? Most likely the paths come
into play because they are encoded in other installed .la files as
dependencies with a wrong path.
But to say for sure one would have to look at the output of the command
with --debug added right after `../libtool'. If you send it, please
pack it (bzip2 or gzip), thanks.
Cheers,
Ralf