Hi Simon, It's during configuration that alsa can't be found. It's not just alsa-utils. Sun Java complains too. Appearantly on ./configure some (most??) packages don't use pkgconfig to figure out the install details of required packages. That's a pitty cause it's so easy and logical.
For some packages I can add configure options that point to the right direction (--with-alsa-prefix). Bit I haven't found it for java yet. There doesn't seem to be a way to point it to the multimedia directory. In fact the build instructions point out that libasound.so should be installed in the /usr/lib directory. So you couldn't even use the /usr/local if you wanted to. By posting, I wasn't really expecting an answer to my question. There is no answer but to install everything into /usr. I just find it a pitty that I'm so limited. Regards, ilja -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Simon Geard Sent: 19 February 2005 10:41 To: BLFS Support List Subject: Re: Multimedia challenge On Fri, 2005-02-18 at 19:06 +0000, ilja wrote: > So what exactly are the pkgconfig entries for? If you open alsa.pc you find > all the details on where to find alsa. Why are programs not using this info? Pkgconfig is a development tool - it's used in configure scripts to obtain information about other packages that might be required - typically, that information includes parameters that should be passed to the compiler and linker such as the location of necessary header files and libraries. Note that it's only relevant at compile time - pkgconfig has no relevance when it comes to running programs. Can you be a bit more specific about the problems you're encountering? You say alsa-utils can't find the alsa-libs - when? Is it the configure stage that can't find them? Make? Or does it just not work when you try to run? For what it's worth though, splitting things into subdirectories can be problematic, since at best, it means a lot of fiddling with environment variables and build parameters to make things see each other. Worse, some packages simply won't work if not installed together - e.g tempting as it might be to put Gtk+ in /usr but put Gnome in /opt/gnome, it inevitably causes problems like icons and toolbars not appearing, themes not working, etc. Simon. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
