[Alsa-user] Cross-compiling Problems
Brought to you by:
perex
From: Douglas J. <do...@tt...> - 2010-12-03 07:37:38
|
When cross-building a system, I cross-build packages into a staging area, which gets put into a nifty initrd. I have always copied the target glibc libs from the cross-gcc tool chain's target files area into the staging area, before cross-building any packages. I don't know why, but that's what I do. :) But alsa-libs and alsa-utils have an error when cross building: cannot find /usr/lib/libc_nonshared.a If I *do not* copy the target glibc libs from the cross-gcc tool chain's target files area into the staging area, then the alsa packages seem to properly cross-build. Is this the sort thing that comes from putting the target glibc libs into the staging area? I have a feeling that the alsa packages' DESTDIR=<staging area> is not properly used in their "make install". Thanks for any clues someone can give me about understanding this problem. |