[alsa-devel] additional problem

[David Henderson]

On 07/11/2011 11:17 AM, Takashi Iwai wrote:
> At Mon, 11 Jul 2011 11:13:03 -0400,
> David Henderson wrote:
>> On 07/11/2011 11:12 AM, Takashi Iwai wrote:
>>> At Mon, 11 Jul 2011 11:05:11 -0400,
>>> David Henderson wrote:
>>>> On 07/11/2011 10:43 AM, Takashi Iwai wrote:
>>>>> At Mon, 11 Jul 2011 10:26:05 -0400,
>>>>> David Henderson wrote:
>>>>>> On 07/01/2011 02:41 AM, Takashi Iwai wrote:
>>>>>>> At Thu, 30 Jun 2011 08:15:41 -0400,
>>>>>>> David Henderson wrote:
>>>>>>>> On 06/29/2011 09:57 AM, David Henderson wrote:
>>>>>>>>> Hi gang!  I've successfully been able to compile the alsa-utils
>>>>>>>>> package with the
>>>>>>>>> "--with-alsa-inc-prefix=/opt/staging/alsa/var/share/include
>>>>>>>>> --with-alsa-prefix=/opt/staging/alsa/lib", but the problem I'm having
>>>>>>>>> now is that the compiled binaries are looking for those directories
>>>>>>>>> during run-time and not just compile-time.  Does anyone have any
>>>>>>>>> thoughts on using those directories for package creation, but that the
>>>>>>>>> software doesn't use the '/opt/staging/alsa' prefix during run-time?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Dave
>>>>>>>> bump for help
>>>>>>> It works usually as is.  Check once via ldd whether the binary is
>>>>>>> really linked with that fixed path.  You may hit a problem when using
>>>>>>> libtool with *.la files, for example.
>>>>>>>
>>>>>>>
>>>>>>> Takashi
>>>>>> Thanks for the continued help Takashi.  I've performed the requested
>>>>>> steps, but all referenced libs are correct (e.g. /lib/... and not
>>>>>> /opt/staging/alsa/lib/...).  Any other thoughts?
>>>>> Check ldd output of the binary.  If it contains the /opt/ path, it
>>>>> means that the path is set statically into the binary.  The old
>>>>> libtool had a related problem, IIRC.
>>>>>
>>>>> Other than that, rather ask your distro.  It's really distro-specific.
>>>>>
>>>>>
>>>>> Takashi
>>>> Hey Takashi, I performed the requested steps, but the output is still
>>>> correct (e.g. /lib/... and not /opt/staging/alsa/lib/...).
>>> So, what shows ldd at all?  Too little information.
>>>
>>>
>>> Takashi
>>
>> # ldd /bin/amixer
>>           linux-gate.so.1 =>   (0xb7768000)
>>           libm.so.6 =>  /lib/libm.so.6 (0xb7741000)
>>           libasound.so.2 =>  /lib/libasound.so.2 (0xb7667000)
>>           libdl.so.2 =>  /lib/libdl.so.2 (0xb7663000)
>>           libpthread.so.0 =>  /lib/libpthread.so.0 (0xb764b000)
>>           libc.so.6 =>  /lib/libc.so.6 (0xb7507000)
>>           /lib/ld-linux.so.2 (0xb7769000)
>>           librt.so.1 =>  /lib/librt.so.1 (0xb74fe000)
> Then what happens if you run /bin/amixer ?
>
>
> Takashi

# /bin/amixer
ALSA lib conf.c:3601:(snd_config_update_r) Cannot access file 
/opt/staging/package/var/share/alsa/alsa.conf
ALSA lib control.c:902:(snd_ctl_open_noupdate) Invalid CTL default
amixer: Mixer attach default error: No such file or directory

Dave