George, here is what I found out:
Since source and destination drives are not identical, you cannot
use DD even if you are dd'ing partition to partition. The reason is
that the two drives will not have the same block map. If the booter
is expecting some info to be at some particular block number, it will
probably not be there on the cloned destination. Sometimes, absolute
block numbers are used (i.e. from start of track0, sector 0). So,
non-identical drives will not work. This is also the same with
the secondary and tertiary booters in /boot/grub.
So, the gist of what I am gathering from various sources is that
non-identical drives should not be cloned via dd.
Ivan Cheng wrote:
Thanks for your reply.
In my target board, alsa version is
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
and from the configure.log:
1316 #include <alsa/asoundlib.h>
1317 #if !((SND_LIB_MAJOR == 1) && (SND_LIB_MINOR == 0))
1318 #error "alsa version != 1.0.x"
1319 #endif
1320 int main(void) { return 0; }
1321
1322 gcc -Wall -Wno-switch -Wpointer-arith -Wredundant-decls -O4 -pipe
-ffast-math -fomit-frame-pointer
-I/home/ivancheng/project/ltib/rootfs/usr/include/ -static
-L/home/ivancheng/project/ltib/rootfs/usr/lib/ -o
/tmp/mplayer-conf-1690-32085 /tmp/mplayer-conf-28369-3 2085.c -lasound
-ldl -lpthread
1323
/opt/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/lib/gcc/arm-no
ne-linux-gnueabi/4.1.2/../../../../arm-none-linux-gnueabi/bin/ld: cannot
find -lasound
1324 collect2: ld returned 1 exit status
It looks like it is my toolchain that is not set up correctly....
Thanks anyway.
Ivan
On Fri, Jun 19, 2009 at 3:06 AM, just4emmett <just4emmett@xxxxxxxxx> wrote:
I want to cross compile it for ARM platform, where it target to support
alsa and directfb. But it is configured to unsupported when I compile it,
even if I configured with --enable-alsa --enable-directfb. Any ideas?
I don't think --enable-alsa will work. When you invoke configure, add the
following options that point to the target files, not the host. That way
configure can autodetect the correct environment.
--with-extralibdir=/path/to/lib/files/on/target
--with-extraincdir=/path/to/include/files/on/target
I also used the following configure options for cross-compiling:
--enable-cross-compile
--cc=your-target-gcc
--host-cc=/usr/bin/gcc
Hope this helps!
_______________________________________________
MPlayer-users mailing list
MPlayer-users@xxxxxxxxxxxx
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
_______________________________________________
MPlayer-users mailing list
MPlayer-users@xxxxxxxxxxxx
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
_______________________________________________
MPlayer-users mailing list
MPlayer-users@xxxxxxxxxxxx
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
