From: James Shatto <wwwshad...@gmail.com>
Subject: Re: [Alsa-user] First post
Date: Sun, 19 Jun 2011 15:36:59 -0500

> A) If you want to overwrite your existing distro's versions, you
> probably want the --prefix=/usr option on your ./configure commands.
> If not, be sure to change your $PATH to look at /usr/local FIRST.
> 
> B) Compile alsa-lib first, alsa-driver second.  Most compile options
> only need --prefix=/usr if you want to override the default of
> /usr/local.  But alsa-driver requires extra parms depending on what
> you want.  Some packages are only tool sets, so make -f Makefile?  And
> use them from where you made them, or copy/move them to more common
> $PATH's.
> 
> C) You might have versioning conflicts depending on what you're trying
> to mix and match.  libc and other things might not work well together
> unless you're running the latest and greatest of every component.  And
> even that is problematic some of the time.
> 
> D) unless you have a lot of time to waste, or just need the learning,
> I'd recommend going with existing distros.  There's enough of them
> that one might suit your current needs.  www.distrowatch.com
  I suggested something intermediary : lfs or gentoo which are
  easily customizable.

  Pierre




> 
> HTH,
> - James
> 
> 
> 
> On 6/19/11, David Henderson <dhender...@digital-pipe.com> wrote:
>> Thanks for the reply Pierre.  I checked into the blfs book, but it
>> merely says "these five chapters will cover alsa" and then gives you a
>> basic "type configure && make".  This is obviously not going to answer
>> the questions below. :)  Any other thoughts?
>>
>> Dave
>>
>>
>> On 06/19/2011 11:22 PM, Pierre Lorenzon wrote:
>>> Hi,
>>>
>>> It looks like to me such questions are well answered in the
>>> blfs book. I personnaly think that the latter is a very good
>>> tool to build his own custom distro.
>>>
>>> Bests
>>>
>>> Pierre
>>>
>>>
>>> From: David Henderson<dhender...@digital-pipe.com>
>>> Subject: [Alsa-user] First post
>>> Date: Sun, 19 Jun 2011 14:41:08 -0400
>>>
>>>> Hi everyone!  I'm currently expanding my knowledge of GNU/Linux to
>>>> include building packages from scratch towards an overall goal of a
>>>> custom distro.  So far, I have a nice base for a command line OS, but
>>>> want to expand into the multimedia aspect.  Alsa was my first (only?)
>>>> choice for the audio portion, but I'm running into problems.  The alsa
>>>> site is somewhat overwhelming to newbies and is easy to get lost.  I
>>>> have a few questions below from which I hope I can find help.  All
>>>> contributions are greatly appreciated. :)
>>>>
>>>> Thanks,
>>>> Dave
>>>>
>>>>
>>>> 1) Currently I have downloaded alsa-driver, alsa-lib, and alsa-utils
>>>> packages.  Is there an order in which these packages need to be compiled
>>>> and installed?
>>>>
>>>> 2) I'm currently running the relatively new Linux kernel 2.6.33 so do I
>>>> need the alsa-driver package?
>>>>
>>>> 3) I've been able to successfully compile the alsa-lib package and
>>>> install it in the custom distro.  When I try to compile the alsa-utils
>>>> package, I constantly get the error:
>>>>
>>>> checking for libasound headers version>= 1.0.16... not present.
>>>> configure: error: Sufficiently new version of libasound not found.
>>>>
>>>> I'm actually using an existing Kubuntu installation to build the
>>>> packages for my custom distro.  As a result, after I compiled the newer
>>>> alsa-lib, I didn't install the package into the Kubuntu OS, but rather a
>>>> staging directory (/opt/staging/alsa).  I'm sure the reason this is
>>>> failing is because it's probably looking for /usr/lib/... or some other
>>>> default location.  How do I tell the configure script for the alsa-utils
>>>> to look in the staging directory for the header files it needs?
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> EditLive Enterprise is the world's most technically advanced content
>>>> authoring tool. Experience the power of Track Changes, Inline Image
>>>> Editing and ensure content is compliant with Accessibility Checking.
>>>> http://p.sf.net/sfu/ephox-dev2dev
>>>> _______________________________________________
>>>> Alsa-user mailing list
>>>> Alsa-user@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/alsa-user
>>
>> ------------------------------------------------------------------------------
>> EditLive Enterprise is the world's most technically advanced content
>> authoring tool. Experience the power of Track Changes, Inline Image
>> Editing and ensure content is compliant with Accessibility Checking.
>> http://p.sf.net/sfu/ephox-dev2dev
>> _______________________________________________
>> Alsa-user mailing list
>> Alsa-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/alsa-user
>>
> 
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-user

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to