I did get the static alsalib calls to not reference the silly directory - at the expense of the PLUGHW functionailty. I can live with that for now. if you want the gory details read on:
===============================================
Spoiler:
Err... Config.h in alsa dir
/* directory containing ALSA configuration database */
#define ALSA_CONFIG_DIR "/usr/share/alsa"
What am I doing wrong? sigh...
I'll keep digging.
EDIT: Hmm. the config.log line 1101 datarootdir='
${prefix}/share' looks suspicious...
Might have a fiddle with that.
EDIT: I see a
datadir = ${prefix}/share in the Makefile...
perhaps I should just give
datadir = /usr/share a go
What's the worst that could happen
FROM:
http://www.gnu.org/prep/standards/ht...Variables.html
Code:
‘datadir’
The directory for installing idiosyncratic read-only architecture-independent
data files for this program. This is usually the same place as ‘datarootdir’,
but we use the two separate variables so that you can move these program-specific
files without altering the location for Info files, man pages, etc.
This should normally be ‘/usr/local/share’, but write it as ‘$(datarootdir)’.
(If you are using Autoconf, write it as ‘@datadir@’.)
The definition of ‘datadir’ is the same for all packages, so you should install
your data in a subdirectory thereof. Most packages install their data under
‘$(datadir)/package-name/’.
EDIT: Just so we are clear, I am out of my depth here
EDIT: Well. I think I fixed it. access to the
hw pcm works anyways without fault for now.
The
plughw no longer seems happy.
I did check the version of the Alsalib I built it against: and that's the 13 build.
For now I will rollback my stuff to just use the
hw port and look at the issue again so the demos are working.