ALSA 1.0.15rc1

ALSA 1.0.15rc1

[Jaroslav Kysela]

Hi all,

	ALSA 1.0.15rc1 packages are released. Please, check 
http://www.alsa-project.org for download and changelog.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs

Re: ALSA 1.0.15rc1

[Thierry Vignaud]

Jaroslav Kysela <perex@suse.cz> writes:

> Hi all,
> 
> 	ALSA 1.0.15rc1 packages are released. Please, check 
> http://www.alsa-project.org for download and changelog.
> 
> 						Jaroslav

Looks like you included the 1.0.14 changelog too. Eg, below shouldn't
have you killed everythinkg after "release 1.0.14a"?

http://www.alsa-project.org/main/index.php/Changes_v1.0.14_v1.0.15rc1#alsa-lib


[edit]alsa-lib
[edit]Core
 Fix plugin directory 
 Properly disable -Bsymbolic-functions if ld doesn't support 
 release 1.0.14a 
 Fix the build of lfloat plugin 
 release 1.0.14 
 Fix undefined references in namehint.c 
 Create asoundlib.h dynamically according to configure options 
 Fix a typo in configure script 
 Continue build even if python-config doesn't exist 
 mixer simple basic abstraction - added python binding 
 Split mmap-emulation code from hw layer

Re: ALSA 1.0.15rc1

[Thierry Vignaud]

Thierry Vignaud <tvignaud@mandriva.com> writes:

> > 	ALSA 1.0.15rc1 packages are released. Please, check 
> > http://www.alsa-project.org for download and changelog.
> > 
> > 						Jaroslav
> 
> Looks like you included the 1.0.14 changelog too. Eg, below shouldn't
> have you killed everythinkg after "release 1.0.14a"?
> 
> http://www.alsa-project.org/main/index.php/Changes_v1.0.14_v1.0.15rc1#alsa-lib

in fact, even "Fix plugin directory" & "Properly disable
-Bsymbolic-functions if ld doesn't support" looks part of 1.0.14a

Re: ALSA 1.0.15rc1

[Jaroslav Kysela]

On Fri, 31 Aug 2007, Thierry Vignaud wrote:

> Thierry Vignaud <tvignaud@mandriva.com> writes:
> 
> > > 	ALSA 1.0.15rc1 packages are released. Please, check 
> > > http://www.alsa-project.org for download and changelog.
> > > 
> > > 						Jaroslav
> > 
> > Looks like you included the 1.0.14 changelog too. Eg, below shouldn't
> > have you killed everythinkg after "release 1.0.14a"?
> > 
> > http://www.alsa-project.org/main/index.php/Changes_v1.0.14_v1.0.15rc1#alsa-lib
> 
> in fact, even "Fix plugin directory" & "Properly disable
> -Bsymbolic-functions if ld doesn't support" looks part of 1.0.14a

It's changelog between 1.0.14 and 1.0.15rc1 not 1.0.14a and 1.0.15rc1.
I can remove 1.0.14a changes, but then the changelog name might be 
confusing.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs

compilation faillure (was: Re: ALSA 1.0.15rc1)

[Thierry Vignaud]

Jaroslav Kysela <perex@suse.cz> writes:

> 	ALSA 1.0.15rc1 packages are released. Please, check 
> http://www.alsa-project.org for download and changelog.

(...)
Making all in simple
make[3]: Entering directory `/home/tv/rpm/BUILD/alsa-lib-1.0.15rc1/modules/mixer/simple'
if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include   -g -O
2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer
 -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF ".deps/python.Tpo" -c -o python.lo python.
c; \
        then mv -f ".deps/python.Tpo" ".deps/python.Plo"; else rm -f ".deps/python.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include -g -O2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF .deps/python.Tpo -c python.c  -DPIC -fPIC -DPIC -o .libs/python.o
ICECC[32088] 14:23:50: can't send joblocalmsg to daemon
python.c:26:27: error: python/Python.h: No such file or directory

>From where does come this header?
Also this shows that configure.in misses some test...

Re: compilation faillure (was: Re: ALSA 1.0.15rc1)

[Takashi Iwai]

At Fri, 31 Aug 2007 14:25:38 +0200,
Thierry Vignaud wrote:
> 
> Jaroslav Kysela <perex@suse.cz> writes:
> 
> > 	ALSA 1.0.15rc1 packages are released. Please, check 
> > http://www.alsa-project.org for download and changelog.
> 
> (...)
> Making all in simple
> make[3]: Entering directory `/home/tv/rpm/BUILD/alsa-lib-1.0.15rc1/modules/mixer/simple'
> if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include   -g -O
> 2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer
>  -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF ".deps/python.Tpo" -c -o python.lo python.
> c; \
>         then mv -f ".deps/python.Tpo" ".deps/python.Plo"; else rm -f ".deps/python.Tpo"; exit 1; fi
>  gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include -g -O2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF .deps/python.Tpo -c python.c  -DPIC -fPIC -DPIC -o .libs/python.o
> ICECC[32088] 14:23:50: can't send joblocalmsg to daemon
> python.c:26:27: error: python/Python.h: No such file or directory
> 
> From where does come this header?
> Also this shows that configure.in misses some test...

Maybe python headers need -Ixxx cc option?
configure script seems not checking the output of python-config
--cflags.

As a workaround, build with --disable-python.


Takashi

Re: compilation faillure

[Thierry Vignaud]

Thierry Vignaud <tvignaud@mandriva.com> writes:

> > 	ALSA 1.0.15rc1 packages are released. Please, check 
> > http://www.alsa-project.org for download and changelog.
> 
> (...)
> Making all in simple
> make[3]: Entering directory `/home/tv/rpm/BUILD/alsa-lib-1.0.15rc1/modules/mixer/simple'
> if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include   -g -O
> 2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer
>  -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF ".deps/python.Tpo" -c -o python.lo python.
> c; \
>         then mv -f ".deps/python.Tpo" ".deps/python.Plo"; else rm -f ".deps/python.Tpo"; exit 1; fi
>  gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include -g -O2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF .deps/python.Tpo -c python.c  -DPIC -fPIC -DPIC -o .libs/python.o
> ICECC[32088] 14:23:50: can't send joblocalmsg to daemon
> python.c:26:27: error: python/Python.h: No such file or directory
> 
> >From where does come this header?
> Also this shows that configure.in misses some test...

looks like it doesn't use python-config at all :-(

Re: compilation faillure (was: Re: ALSA 1.0.15rc1)

[Jaroslav Kysela]

On Fri, 31 Aug 2007, Thierry Vignaud wrote:

> Jaroslav Kysela <perex@suse.cz> writes:
> 
> > 	ALSA 1.0.15rc1 packages are released. Please, check 
> > http://www.alsa-project.org for download and changelog.
> 
> (...)
> Making all in simple
> make[3]: Entering directory `/home/tv/rpm/BUILD/alsa-lib-1.0.15rc1/modules/mixer/simple'
> if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include   -g -O
> 2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer
>  -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF ".deps/python.Tpo" -c -o python.lo python.
> c; \
>         then mv -f ".deps/python.Tpo" ".deps/python.Plo"; else rm -f ".deps/python.Tpo"; exit 1; fi
>  gcc -DHAVE_CONFIG_H -I. -I. -I../../../include -I../../../include -g -O2 -W -Wall -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT python.lo -MD -MP -MF .deps/python.Tpo -c python.c  -DPIC -fPIC -DPIC -o .libs/python.o
> ICECC[32088] 14:23:50: can't send joblocalmsg to daemon
> python.c:26:27: error: python/Python.h: No such file or directory

Oops, configure script does not detected location of python C header files. 
Fixed in HG.

You may disable building of python code with --disable-python and wait for 
1.0.15rc2.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs

Re: compilation faillure

[Jaroslav Kysela]

On Fri, 31 Aug 2007, Thierry Vignaud wrote:

> looks like it doesn't use python-config at all :-(

It was used only for libraries not C header files. My mistake. Thanks for 
the notification.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs

Re: ALSA 1.0.15rc1

[Thierry Vignaud]

Jaroslav Kysela <perex@suse.cz> writes:

> > > > 	ALSA 1.0.15rc1 packages are released. Please, check 
> > > > http://www.alsa-project.org for download and changelog.
> > > > 
> > > > 						Jaroslav
> > > 
> > > Looks like you included the 1.0.14 changelog too. Eg, below shouldn't
> > > have you killed everythinkg after "release 1.0.14a"?
> > > 
> > > http://www.alsa-project.org/main/index.php/Changes_v1.0.14_v1.0.15rc1#alsa-lib
> > 
> > in fact, even "Fix plugin directory" & "Properly disable
> > -Bsymbolic-functions if ld doesn't support" looks part of 1.0.14a
> 
> It's changelog between 1.0.14 and 1.0.15rc1 not 1.0.14a and 1.0.15rc1.
> I can remove 1.0.14a changes, but then the changelog name might be 
> confusing.

You got a point.
Still, it looks like bogus order:
- 1.0.14a changes
- 1.0.14 changes
- 1.0.15 changes

Re: compilation faillure

[Thierry Vignaud]

Jaroslav Kysela <perex@suse.cz> writes:

> Oops, configure script does not detected location of python C header files. 
> Fixed in HG.
> 
> You may disable building of python code with --disable-python and wait for 
> 1.0.15rc2.

--disable-python has no effect
--disable-python &  --enable-python breaks at the exact same point...

Re: compilation faillure

[Takashi Iwai]

At Fri, 31 Aug 2007 15:32:06 +0200,
Thierry Vignaud wrote:
> 
> Jaroslav Kysela <perex@suse.cz> writes:
> 
> > Oops, configure script does not detected location of python C header files. 
> > Fixed in HG.
> > 
> > You may disable building of python code with --disable-python and wait for 
> > 1.0.15rc2.
> 
> --disable-python has no effect

Works for me.


Takashi

Re: ALSA 1.0.15rc1

[Elimar Riesebieter]

On Fri, 31 Aug 2007 the mental interface of
Jaroslav Kysela told:

>Hi all,
>
>	ALSA 1.0.15rc1 packages are released. Please, check 
>http://www.alsa-project.org for download and changelog.

Now we have the changelog formatted in xhtml. We (Debian) are
distributing the changes always in pure text format, otherwise we
have to put a browser to the install deps. I tried to convert with
html2text but got some garbage. Is there a tool to extract the text
similar formatted as the old "v1-0-14rc4--v1-0-14.txt"? Isn't it
usual to package a changelog to the sources?

Elimar


-- 
   Obviously the human brain works like a computer.
   Since there are no stupid computers humans can't be stupid.
   There are just a few running with Windows or even CE ;-)

Re: compilation faillure

[stan]

Thierry Vignaud wrote:
> Jaroslav Kysela <perex@suse.cz> writes:
>
>   
>> Oops, configure script does not detected location of python C header files. 
>> Fixed in HG.
>>
>> You may disable building of python code with --disable-python and wait for 
>> 1.0.15rc2.
>>     
>
> --disable-python has no effect
> --disable-python &  --enable-python breaks at the exact same point...
> _______________________________________________
>
>   
Hi,

When I compile the snapshots on Fedora they fail with python errors 
unless I go to the /usr/include directory and create a symbolic link: ln 
-s python2.5 python
i.e. create a generic python link to the version specific include 
directory.  Your system might need something similar.

Re: ALSA 1.0.15rc1

[Elimar Riesebieter]

On Fri, 31 Aug 2007 the mental interface of
Elimar Riesebieter told:

[...]
> Is there a tool to extract the text similar formatted as the old
> "v1-0-14rc4--v1-0-14.txt"? Isn't it usual to package a changelog to
> the sources?

Well using lynx (print to file) and some vim actions are doing the
trick, But anyway, shouldn't it be included in sources?

Elimar

-- 
     .~.
     /V\   L   I   N   U   X
    /( )\ >Phear the Penguin<
    ^^-^^

Re: ALSA 1.0.15rc1

[Jaroslav Kysela]

On Fri, 31 Aug 2007, Elimar Riesebieter wrote:

> On Fri, 31 Aug 2007 the mental interface of
> Elimar Riesebieter told:
> 
> [...]
> > Is there a tool to extract the text similar formatted as the old
> > "v1-0-14rc4--v1-0-14.txt"? Isn't it usual to package a changelog to
> > the sources?
> 
> Well using lynx (print to file) and some vim actions are doing the
> trick, But anyway, shouldn't it be included in sources?

It's probably better to extract the wiki source text from <textarea> tag 
when you download the edit page (only html entities like &lt; etc. should 
be converted back to text):

http://www.alsa-project.org/main/index.php?title=Changes_v1.0.14_v1.0.15rc1&action=edit

Actually, I have no plans to add this history to source files. Anyone can 
get this information from www or extract it from the HG repository.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs