From: tdavis@dsl-only.net
To: stan <stanl@cox.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Install of alsa 1.0.14.final on Fedora 7
Date: Sat, 14 Jul 2007 08:15:37 -0700 [thread overview]
Message-ID: <20070714081537.ayf2b2byrxq88kok@webmail.dsl-only.net> (raw)
In-Reply-To: <20070714072701.057106a3@localhost.localdomain>
Quoting stan <stanl@cox.net>:
> On Sat, 14 Jul 2007 00:09:31 -0700
> tdavis@dsl-only.net wrote:
>
>> Quoting stan <stanl@cox.net>:
>>
>> > On Fri, 13 Jul 2007 08:53:47 -0700
>> > tdavis@dsl-only.net wrote:
>> >
>> >> For RPM based systems, I have a build environment for the drivers,
>> >> libs, and utils packages at
>> >> http://members.dsl-only.net/~tdavis/my-build.tar.bz2. You need to
>> >> be root to build them, but they won't interfere with your rpm
>> >> distribution. THe driver rpm will also make a backup of your
>> >> current drivers prior to installation.
>> >>
>> >> Tobin
>> >>
>> >
>> > Hi Tobin,
>> >
>> > I unpacked the archive and typed make. It created 4 RPMs.
>> > Two of them installed, alsa-lib and alsa-lib-devel. When I run a
>> > test on the drivers rpm, there are conflicts with the kernel
>> > headers already on the box. And I have no sound now, except in the
>> > audio configuration screen which is using the 14.rc3 packages. The
>> > packages are named with rh7 instead of fc7 as well.
>> >
>> > Do I have to run make install to get everything working, or is the
>> > header incompatability in the drivers a show stopper?
>> >
>> >
>> >
>> > Thanks.
>> > _______________________________________________
>> > Alsa-devel mailing list
>> > Alsa-devel@alsa-project.org
>> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>> >
>>
>> I'll have to look at the rpm build process to see why they are named
>> RH7 instead of FC7. To install, you should just type "audio_install".
>>
>> If there is a conflict, just type "rpm -Uvh <package> --force".
>>
> Thanks Tobin. I was going to upgrade to the latest kernel to see if
> the header conflicts would go away. All of the conflicts seem to be
> alsa related (surprise, surprise) so should have only positive effect
> on compiles. I was concerned about a package update for alsa and what
> these different files would do. Should I remove the alsa 14.rc3
> packages?
Yes. I just looked at the audio_install script again, and it doesn't
upgrade, just forces it's way in (not my script). I also haven't had
a chance to work with Fedora Core in a while.
When I get back home on Monday (I'm monitoring email while on a sudo
vacation), I'll install it in a VM on my desktop system and fix the
packaging system to recognize that distro.
Tobin
next prev parent reply other threads:[~2007-07-14 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 19:48 Install of alsa 1.0.14.final on Fedora 7 stan
2007-07-14 7:09 ` tdavis
2007-07-14 14:27 ` stan
2007-07-14 15:15 ` tdavis [this message]
2007-07-14 22:41 ` stan
2007-07-15 19:47 ` stan
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=20070714081537.ayf2b2byrxq88kok@webmail.dsl-only.net \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=stanl@cox.net \
/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.