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.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
