another build problem on current cvs

[Joris Huizer]

Hello,

For the past week or so, building from cvs on a debian/stable system w/ 
alsa installed (using a custom kernel Linux debian 2.4.18.041216) breaks 
on alsa-specific code in wine;
I attached the log; note that I did a `cvs update -dPA` and `make 
distclean` so this can't be any problem with the source I have

Any ideas? Maybe you can point me to a place where I can read how to fix 
this properly (I never worked on alsa-specific code before...) or 
something like that

regards,

Joris

[Vincent Béron]

Le mar 28/12/2004 à 09:24, Joris Huizer a écrit :
> Hello,
>
> For the past week or so, building from cvs on a debian/stable system w/ 
> alsa installed (using a custom kernel Linux debian 2.4.18.041216) breaks 
> on alsa-specific code in wine;
> I attached the log; note that I did a `cvs update -dPA` and `make 
> distclean` so this can't be any problem with the source I have
>
> Any ideas? Maybe you can point me to a place where I can read how to fix 
> this properly (I never worked on alsa-specific code before...) or 
> something like that

Which version of ALSA do you have headers for?

Vincent

[Joris Huizer]

Vincent Béron wrote:
> Le mar 28/12/2004 à 09:24, Joris Huizer a écrit :
> > Hello,
> >
> > For the past week or so, building from cvs on a debian/stable system w/ 
> > alsa installed (using a custom kernel Linux debian 2.4.18.041216) breaks 
> > on alsa-specific code in wine;
> > I attached the log; note that I did a `cvs update -dPA` and `make 
> > distclean` so this can't be any problem with the source I have
> >
> > Any ideas? Maybe you can point me to a place where I can read how to fix 
> > this properly (I never worked on alsa-specific code before...) or 
> > something like that
>
> Which version of ALSA do you have headers for?
>
> Vincent

In debian the package is called libasound2-dev, version 
"0.9.0beta10.9.0beta1" which should be the 0.9 branch of alsa

Joris

[Vincent Béron]

Le mer 29/12/2004 à 05:38, Joris Huizer a écrit :
[snip]
> In debian the package is called libasound2-dev, version 
> "0.9.0beta10.9.0beta1" which should be the 0.9 branch of alsa

I thought we stopped supporting alsa 0.9 a while ago to focus on alsa
1.0...

(Looking through dlls/winmm/winealsa/audio.c's changelog, it's been that
way since snapshot 20040505).

The two versions use the same function names but with different number
of args (hence the problems which you saw).

Either update to alsa 1.0, downgrade Wine to prior 20040505, or switch
to the wineoss driver.

Vincent

[Ferenc Wagner]

Vincent Béron <vberon(a)mecano.gme.usherb.ca> writes:
> Le mer 29/12/2004 à 05:38, Joris Huizer a écrit :
> > In debian the package is called libasound2-dev, version 
> > "0.9.0beta10.9.0beta1" which should be the 0.9 branch of alsa
>
> Either update to alsa 1.0, downgrade Wine to prior
> 20040505, or switch to the wineoss driver.

For Debian stable I've got some unofficial ALSA packages
(among others) at http://afavant.elte.hu/~wferi/debian/
which may come handy.
-- 
Feri.

[Andreas Mohr]

Hi,

On Wed, Dec 29, 2004 at 06:42:41PM -0500, Vincent Béron wrote:
> Le mer 29/12/2004 à 05:38, Joris Huizer a écrit :
> [snip]
> > In debian the package is called libasound2-dev, version 
> > "0.9.0beta10.9.0beta1" which should be the 0.9 branch of alsa
>
> I thought we stopped supporting alsa 0.9 a while ago to focus on alsa
> 1.0...
>
> (Looking through dlls/winmm/winealsa/audio.c's changelog, it's been that
> way since snapshot 20040505).
>
> The two versions use the same function names but with different number
> of args (hence the problems which you saw).
>
> Either update to alsa 1.0, downgrade Wine to prior 20040505, or switch
> to the wineoss driver.
> Problem is that we might want to have Wine never break during compile.
> At least for semi-modern software versions it should compile successfully,
> no matter how much functionality we have to disable to achieve that.

Configure check, anyone?

Andreas Mohr

[Vincent Béron]

Le sam 01/01/2005 à 09:20, Andreas Mohr a écrit :
[snip]
> Problem is that we might want to have Wine never break during compile.
> At least for semi-modern software versions it should compile successfully,
> no matter how much functionality we have to disable to achieve that.

Right.
> Configure check, anyone?

To disable Alsa if alsa 0.9x headers are detected?

I don't have either 0.9.x or 1.0 here, so I'd prefer somebody who has at
least one of them to change configure.ac.

Vincent

[Vincent Béron]

Le dim 02/01/2005 à 20:24, Vincent Béron a écrit :
> Le sam 01/01/2005 à 09:20, Andreas Mohr a écrit :
> [snip]
> > Problem is that we might want to have Wine never break during compile.
> > At least for semi-modern software versions it should compile successfully,
> > no matter how much functionality we have to disable to achieve that.
>
> Right.
> > Configure check, anyone?
>
> To disable Alsa if alsa 0.9x headers are detected?
>
> I don't have either 0.9.x or 1.0 here, so I'd prefer somebody who has at
> least one of them to change configure.ac.

Found a computer with 1.0, but haven't found one with 0.9, so it's not
actually tested with 0.9, but I think it does.

Changelog:
Only use Alsa if 1.0 is detected.

Vincent