Hi Ady, thanks for contributing to the conversation. :) I have a couple of questions based on your response below... Why do I need to use the new system for compiling? Isn't there normally 'configure' and 'make' options that allow for compiling on one system so the software can be packaged for installation on another system (e.g. DESTDIR)? The custom distro doesn't use .deb packages or any other existing package manager. I think James was referring to obtaining certain packages in Kubuntu (which is .deb based) so the alsa packages could be compiled on it and migrated over to the custom distro. I appreciate you guys steering me in the direction of using existing distro's, but there are several reasons to "roll my own". And the reasons I don't want to join an existing project is because 1) there isn't another distro like the one I'm building as I've looked 2) instead of having to debate/argue with existing members over implementing changes, I can just re-route the time and headache into figuring out how to build my own. lol Some may consider this a misuse of resources, but if nobody was adventurous enough to break away from the norm, we've never have innovation. :) Again, I appreciate you guys trying to steer me in the direction most should go, but it isn't the route for everyone. :) Dave On 06/20/2011 04:06 AM, Ady Deac wrote: > ... or Sorcerer. > > James, you need to use the new system for compiling, not some other one. > And how do you install applications on your "custom" system? By .deb > packages?!?! Come on, this is not a custom system! This is exactly what > Pierre said: reinventing the wheel. Like Ubuntu for Debian - who needs a > copy when you have the original *for free*!!! > > You might be better using an already established distro, or if you want > to go a little more in-deep, you might want to try a source based > distro: that will definitely help you better understand the linux > environment than what you are trying to do. There are already known > dependencies that these distros will give you the choice to compile in > or not. But doing that all by yourself is really an "misuse of resources". > > If you do have that much free time, why don't you continue an already > existing project? Join a project and ask for work: there will be so much > interesting things you could do that will be over your head in less than > a week after joining any open source project. Just ask! > > Keep up the good work! Work together! > > > On 20.06.2011 18:55, Pierre Lorenzon wrote: >> From: James Shatto<wwwshadow7@xxxxxxxxx> >> Subject: Re: 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<dhenderson@xxxxxxxxxxxxxxxx> 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<dhenderson@xxxxxxxxxxxxxxxx> >>>>> Subject: 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@xxxxxxxxxxxxxxxxxxxxx >>>>>> 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@xxxxxxxxxxxxxxxxxxxxx >>>> 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@xxxxxxxxxxxxxxxxxxxxx >>> 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@xxxxxxxxxxxxxxxxxxxxx >> 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@xxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
