On 27/06/2011, David Henderson <dhenderson@digital-pipe.com> wrote: [...]
checking for libasound headers version>= 1.0.16... not present. configure: error: Sufficiently new version of libasound not found.
Seeing as how this is a staging directory and not the actual place the package is being installed to, I'm having the afore mentioned problem because the alsa-utils package is looking under /... for the header files instead of the /opt/staging/alsa/... directory. Is there a compile-time parameter that I can use so that alsa-utils looks in the staging directory for the header files - just during the compile phase?
Hi Dave, try giving --with-alsa-inc-prefix=/opt/staging/alsa to the configure script. -- Adrian. http://ovejafm.com http://elesquinazotango.com.ar http://www.elarteylatecnologia.com.ar