All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Guanqun <guanqun.lu@intel.com>
To: David Henderson <dhenderson@digital-pipe.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: additional problem
Date: Fri, 1 Jul 2011 01:01:52 +0800	[thread overview]
Message-ID: <20110630170152.GG26397@qtel.sh.intel.com> (raw)
In-Reply-To: <4E0C99B2.3070103@digital-pipe.com>

On Thu, Jun 30, 2011 at 11:43:46PM +0800, David Henderson wrote:
> On 06/30/2011 08:15 AM, 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
> 
> Maybe I'm asking the wrong questions :), so lets try this... what are 
> the recommended steps to compile this software for package maintainers?

I'm not the maintainer, so it might not be correct. They might use some
kind of auto build services, e.g. build.opensuse.org

> 
> Thanks
> Dave
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 
guanqun

  reply	other threads:[~2011-06-30 17:05 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 [this message]
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
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=20110630170152.GG26397@qtel.sh.intel.com \
    --to=guanqun.lu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dhenderson@digital-pipe.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.