Snapshot From ALSA Server

Snapshot From ALSA Server

[Jean-Pierre André]

Hi,

When I try to compile alsa-driver from the snapshot from alsa server
(eg alsa-driver-1.0.19.11.g5fc41.195.g772ce.tar.bz2), the compilation
process fails at applying two patches : pci/hda/hda_beep.patch and
acore/misc.patch

After manually fixing the patches, the compilation goes on and
provides apparently valid modules (at least I get sound from them).

Why is it so ? In the said patches I see nothing specific to my
environment. Could there be a missing patch or overlapping patches
applied in a wrong order ? Are these tarballs compiled before
being made available ?

Note : this problem does not occur in daily snapshots by Tagashi.

Regards

Jean-Pierre

Re: Snapshot From ALSA Server

[Clemens Ladisch]

Jean-Pierre André wrote:
> When I try to compile alsa-driver from the snapshot from alsa server
> (eg alsa-driver-1.0.19.11.g5fc41.195.g772ce.tar.bz2), the compilation
> process fails at applying two patches : pci/hda/hda_beep.patch and
> acore/misc.patch

Fixed now.

> After manually fixing the patches, the compilation goes on and
> provides apparently valid modules (at least I get sound from them).
> 
> Why is it so ?

Because the .c files were changed without updating the patch files.

> Are these tarballs compiled before being made available ?

No; most developers use the alsa-kernel tree.


Best regards,
Clemens
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Re: Snapshot From ALSA Server

[Takashi Iwai]

At Tue, 17 Feb 2009 17:35:49 +0100,
Clemens Ladisch wrote:
> 
> Jean-Pierre André wrote:
> > When I try to compile alsa-driver from the snapshot from alsa server
> > (eg alsa-driver-1.0.19.11.g5fc41.195.g772ce.tar.bz2), the compilation
> > process fails at applying two patches : pci/hda/hda_beep.patch and
> > acore/misc.patch
> 
> Fixed now.
> 
> > After manually fixing the patches, the compilation goes on and
> > provides apparently valid modules (at least I get sound from them).
> > 
> > Why is it so ?
> 
> Because the .c files were changed without updating the patch files.
> 
> > Are these tarballs compiled before being made available ?
> 
> No; most developers use the alsa-kernel tree.

I don't ;)

alsa-driver-snapshot tarball on kernel.org(*) is also not always
checked at updating.  But, it's compiled and built on SUSE
build-service immediately to provide the latest alsa-driver update
packages, so I'll notice build errors sooner or later.


Takashi

*) ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz