From: David Henderson <dhenderson@digital-pipe.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: additional problem
Date: Mon, 11 Jul 2011 11:13:03 -0400 [thread overview]
Message-ID: <4E1B12FF.4080307@digital-pipe.com> (raw)
In-Reply-To: <s5htyasj1gi.wl%tiwai@suse.de>
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)
Dave
next prev parent reply other threads:[~2011-07-11 15:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 13:57 additional problem David Henderson
2011-06-30 12:15 ` David Henderson
2011-06-30 15:43 ` David Henderson
2011-06-30 17:01 ` Lu Guanqun
2011-07-01 6:41 ` Takashi Iwai
2011-07-11 14:26 ` David Henderson
2011-07-11 14:43 ` Takashi Iwai
2011-07-11 15:05 ` David Henderson
2011-07-11 15:12 ` Takashi Iwai
2011-07-11 15:13 ` David Henderson [this message]
2011-07-11 15:17 ` Takashi Iwai
2011-07-11 15:25 ` David Henderson
2011-07-11 15:52 ` Takashi Iwai
2011-07-12 13:05 ` David Henderson
2011-07-12 13:13 ` Takashi Iwai
2011-07-12 13:30 ` David Henderson
2011-07-13 13:14 ` David Henderson
2011-07-13 14:08 ` Takashi Iwai
2011-07-13 14:25 ` David Henderson
2011-07-13 14:31 ` Takashi Iwai
2011-07-22 18:23 ` David Henderson
2011-07-22 19:24 ` Takashi Iwai
2011-06-30 17:34 ` alex dot baldacchino dot alsasub at gmail dot com
2011-06-30 19:02 ` David Henderson
2011-07-01 0:48 ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-11 14:32 ` David Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E1B12FF.4080307@digital-pipe.com \
--to=dhenderson@digital-pipe.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox