From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Henderson Subject: Re: additional problem Date: Mon, 11 Jul 2011 11:05:11 -0400 Message-ID: <4E1B1127.4080800@digital-pipe.com> References: <4E0B2F67.3070304@digital-pipe.com> <4E0C68ED.1070506@digital-pipe.com> <4E1B07FD.9030702@digital-pipe.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-yw0-f51.google.com (mail-yw0-f51.google.com [209.85.213.51]) by alsa0.perex.cz (Postfix) with ESMTP id 0ED95103800 for ; Mon, 11 Jul 2011 17:07:17 +0200 (CEST) Received: by ywa8 with SMTP id 8so1540709ywa.38 for ; Mon, 11 Jul 2011 08:07:17 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org 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/...). As stated in the reply to Alex, the only place that path (from the error message) is used during the compile process is during the 'make' call using DESTDIR. Other than that, the paths are root based and don't use the /opt/staging/alsa prefix. Other thoughts? Dave