rc4 lib - build failing

rc4 lib - build failing

[Jaroslav Kysela]

Hi all,

	could everybody with problems of building alsa library (undefined 
symbol) send me version of ld? (ld --version)? I will try to add a 
detection of faulty ld to the configure script. Thanks.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project  http://www.alsa-project.org
SuSE Linux    http://www.suse.com



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4 lib - build failing

[m]

sure, its GNU ld version 2.11.92.0.12 20011121

should we upgrade our ld? it would explain a *lot* of problems i've had
with compiles if there is a faulty ld out there...

thanks

m


On Wed, 2002-10-23 at 08:57, Jaroslav Kysela wrote:
> Hi all,
> 
> 	could everybody with problems of building alsa library (undefined 
> symbol) send me version of ld? (ld --version)? I will try to add a 
> detection of faulty ld to the configure script. Thanks.
> 
> 						Jaroslav
> 
> -----
> Jaroslav Kysela <perex@suse.cz>
> Linux Kernel Sound Maintainer
> ALSA Project  http://www.alsa-project.org
> SuSE Linux    http://www.suse.com
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future 
> of Java(TM) technology. Join the Java Community 
> Process(SM) (JCP(SM)) program now. 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 
-- 
iriXx
www.iriXx.org

copyleft: creativity, technology and freedom?
info@copyleftmedia.org.uk
www.copyleftmedia.org.uk

 _
( )  ascii ribbon against html email
 X
/ \    cat /dev/sda1 > /dev/dsp


  *** stopping make sense ***



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4 lib - build failing

[Jaroslav Kysela]

On 23 Oct 2002, m wrote:

> sure, its GNU ld version 2.11.92.0.12 20011121

What is your distribution?

> should we upgrade our ld? it would explain a *lot* of problems i've had
> with compiles if there is a faulty ld out there...

Hmm. The situation seems to be more difficult.

ld 2.9.1.0.25	- does not work (SuSE 6.3)
ld 2.10.0.33    - works (SuSE 7.1)

Perhaps, we have a specific patch for binutils..

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project  http://www.alsa-project.org
SuSE Linux    http://www.suse.com



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4 lib - build failing

[m]

On Wed, 2002-10-23 at 10:22, Jaroslav Kysela wrote:
> On 23 Oct 2002, m wrote:
> 
> > sure, its GNU ld version 2.11.92.0.12 20011121
> 
> What is your distribution?

mandrake 8.2
> 
> > should we upgrade our ld? it would explain a *lot* of problems i've had
> > with compiles if there is a faulty ld out there...
> 
> Hmm. The situation seems to be more difficult.
> 
> ld 2.9.1.0.25	- does not work (SuSE 6.3)
> ld 2.10.0.33    - works (SuSE 7.1)
> 
> Perhaps, we have a specific patch for binutils..

hmm... yes, thats interesting.. 

could you please give me a url for the patch?

thanks

m~


-- 
iriXx
www.iriXx.org

copyleft: creativity, technology and freedom?
info@copyleftmedia.org.uk
www.copyleftmedia.org.uk

 _
( )  ascii ribbon against html email
 X
/ \    cat /dev/sda1 > /dev/dsp


  *** stopping make sense ***



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4 lib - build failing

[Takashi Iwai]

At Wed, 23 Oct 2002 09:57:50 +0200 (CEST),
Jaroslav wrote:
> 
> Hi all,
> 
> 	could everybody with problems of building alsa library (undefined 
> symbol) send me version of ld? (ld --version)? I will try to add a 
> detection of faulty ld to the configure script. Thanks.

as i reported before, it looks like a problem of libtool.
libtool doesn't pass -Wl,xx options to linker, although ld itself
supports the versioned symbols.
sorry, i forgot to stress this theme.

well, checking libtool version in configure script would be one of
easy solutions.


Takashi


-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4 lib - build failing

[Jaroslav Kysela]

On Wed, 23 Oct 2002, Takashi Iwai wrote:

> At Wed, 23 Oct 2002 09:57:50 +0200 (CEST),
> Jaroslav wrote:
> > 
> > Hi all,
> > 
> > 	could everybody with problems of building alsa library (undefined 
> > symbol) send me version of ld? (ld --version)? I will try to add a 
> > detection of faulty ld to the configure script. Thanks.
> 
> as i reported before, it looks like a problem of libtool.
> libtool doesn't pass -Wl,xx options to linker, although ld itself
> supports the versioned symbols.
> sorry, i forgot to stress this theme.

And I forgot to your report. Sorry.

> well, checking libtool version in configure script would be one of
> easy solutions.

Doesn't exist a trick for older libtool?

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project  http://www.alsa-project.org
SuSE Linux    http://www.suse.com



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4 lib - build failing

[Takashi Iwai]

At Wed, 23 Oct 2002 12:06:39 +0200 (CEST),
Jaroslav wrote:
> 
> On Wed, 23 Oct 2002, Takashi Iwai wrote:
> 
> > At Wed, 23 Oct 2002 09:57:50 +0200 (CEST),
> > Jaroslav wrote:
> > > 
> > > Hi all,
> > > 
> > > 	could everybody with problems of building alsa library (undefined 
> > > symbol) send me version of ld? (ld --version)? I will try to add a 
> > > detection of faulty ld to the configure script. Thanks.
> > 
> > as i reported before, it looks like a problem of libtool.
> > libtool doesn't pass -Wl,xx options to linker, although ld itself
> > supports the versioned symbols.
> > sorry, i forgot to stress this theme.
> 
> And I forgot to your report. Sorry.
> 
> > well, checking libtool version in configure script would be one of
> > easy solutions.
> 
> Doesn't exist a trick for older libtool?

i couldn't find relevant info in libtool's info text.
and the old libtool code looks also not supporting the extra options.

but it's a bit difficult to check now, because all of my machines at
the office have been already updated...

please note that even without versioned symbols, the compatibility
with rc3 is kept, because we map the new functions with __ prefixes
and use aliases.
of course, this means that the next change wouldn't be compatible.


Takashi


-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[tomasz motylewski]

I have just updated to CVS.

Debian 2.2

I needed to run autoconf; ./configure; make; ./configure; make

cd alsa-driver

./configure
[...]
checking for USB... no
checking for PCMCIA... yes
./configure: ALSA_TOPLEVEL_INIT: command not found
./configure: ALSA_TOPLEVEL_SELECT: command not found
updating cache ./config.cache
creating ./config.status
creating version
creating Makefile.conf
creating snddevices
creating utils/alsa-driver.spec
creating utils/buildrpm
creating toplevel.config
sed: can't read ./toplevel.config.in: No such file or directory
creating include/config.h
creating include/config1.h
cat: ./include/config1.h.in: No such file or directory
creating include/version.h
tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ make
make  all-deps
make[1]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
ln -sf ../alsa-kernel alsa-kernel
gcc -Ialsa-kernel/scripts alsa-kernel/scripts/mod-deps.c -o utils/mod-deps
cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
--makeconf > toplevel.config.in
cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
--acinclude > acinclude.m4
cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
--include > include/config1.h.in
make[1]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'

Please, run the configure script as first...
tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ ./configure 
loading cache ./config.cache
[...]
checking for USB... no
checking for PCMCIA... yes
./configure: ALSA_TOPLEVEL_INIT: command not found
./configure: ALSA_TOPLEVEL_SELECT: command not found
creating ./config.status
creating version
creating Makefile.conf
creating snddevices
creating utils/alsa-driver.spec
creating utils/buildrpm
creating toplevel.config
creating include/config.h
include/config.h is unchanged
creating include/config1.h
creating include/version.h
include/version.h is unchanged
tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ make
if [ ! -d include/sound -a ! -L include/sound ]; then \
  ln -sf ../alsa-kernel/include include/sound ; \
fi
cp -auvf include/version.h include/sound/version.h
include/version.h -> include/sound/version.h
make dep
make[1]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
make[2]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore'
make  -C ioctl32 fastdep
make[3]: Entering directory
`/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/ioctl32'
/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include/sndversions.h was updated
gcc -M -D__KERNEL__ -DMODULE=1
-I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
-I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
-DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
hwdep32.c ioctl32.c pcm32.c rawmidi32.c seq32.c timer32.c > .depend
make[3]: Leaving directory
`/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/ioctl32'
make  -C oss fastdep
make[3]: Entering directory
`/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/oss'
/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include/sndversions.h was not updated
gcc -D__KERNEL__ -DMODULE=1 -I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
-I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
-DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD  -E
-D__GENKSYMS__ mixer_oss.c

- it sems to be OK at this point.

But then:

gcc -M -D__KERNEL__ -DMODULE=1
-I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
-I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
-DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
gus_dma.c gus_dram.c gus_instr.c gus_io.c gus_irq.c gus_lfo.c gus_main.c
gus_mem.c gus_mem_proc.c gus_mixer.c gus_pcm.c gus_reset.c gus_sample.c
gus_simple.c gus_synth.c gus_timer.c gus_uart.c gus_volume.c gusclassic.c
gusextreme.c gusmax.c interwave-stb.c interwave.c > .depend
make[3]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/isa/gus'
make  -C msnd fastdep
make: Entering an unknown directory
make: *** msnd: No such file or directory.  Stop.
make: Leaving an unknown directory
make[2]: *** [_sfdep_msnd] Error 2
make[2]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/isa'
make[1]: *** [dep] Error 1
make[1]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
make: *** [include/sndversions.h] Error 2
tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ 


What is the "true one" method of compling ALSA CVS?

Best regards,
--
Tomasz Motylewski



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[Patrick Shirkey]

tomasz motylewski wrote:
> I have just updated to CVS.
> 
> Debian 2.2
> 
> I needed to run autoconf; ./configure; make; ./configure; make
> 
> cd alsa-driver
> 
> ./configure
> [...]
> checking for USB... no
> checking for PCMCIA... yes
> ./configure: ALSA_TOPLEVEL_INIT: command not found
> ./configure: ALSA_TOPLEVEL_SELECT: command not found
> updating cache ./config.cache
> creating ./config.status
> creating version
> creating Makefile.conf
> creating snddevices
> creating utils/alsa-driver.spec
> creating utils/buildrpm
> creating toplevel.config
> sed: can't read ./toplevel.config.in: No such file or directory
> creating include/config.h
> creating include/config1.h
> cat: ./include/config1.h.in: No such file or directory
> creating include/version.h
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ make
> make  all-deps
> make[1]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> ln -sf ../alsa-kernel alsa-kernel
> gcc -Ialsa-kernel/scripts alsa-kernel/scripts/mod-deps.c -o utils/mod-deps
> cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
> --makeconf > toplevel.config.in
> cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
> --acinclude > acinclude.m4
> cat alsa-kernel/scripts/Modules.dep utils/Modules.dep | utils/mod-deps
> --include > include/config1.h.in
> make[1]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> 
> Please, run the configure script as first...
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ ./configure 
> loading cache ./config.cache
> [...]
> checking for USB... no
> checking for PCMCIA... yes
> ./configure: ALSA_TOPLEVEL_INIT: command not found
> ./configure: ALSA_TOPLEVEL_SELECT: command not found
> creating ./config.status
> creating version
> creating Makefile.conf
> creating snddevices
> creating utils/alsa-driver.spec
> creating utils/buildrpm
> creating toplevel.config
> creating include/config.h
> include/config.h is unchanged
> creating include/config1.h
> creating include/version.h
> include/version.h is unchanged
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ make
> if [ ! -d include/sound -a ! -L include/sound ]; then \
>   ln -sf ../alsa-kernel/include include/sound ; \
> fi
> cp -auvf include/version.h include/sound/version.h
> include/version.h -> include/sound/version.h
> make dep
> make[1]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> make[2]: Entering directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore'
> make  -C ioctl32 fastdep
> make[3]: Entering directory
> `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/ioctl32'
> /home/tom/devel/aeg/ALSA/cvs/alsa-driver/include/sndversions.h was updated
> gcc -M -D__KERNEL__ -DMODULE=1
> -I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
> -I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
> -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
> hwdep32.c ioctl32.c pcm32.c rawmidi32.c seq32.c timer32.c > .depend
> make[3]: Leaving directory
> `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/ioctl32'
> make  -C oss fastdep
> make[3]: Entering directory
> `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/acore/oss'
> /home/tom/devel/aeg/ALSA/cvs/alsa-driver/include/sndversions.h was not updated
> gcc -D__KERNEL__ -DMODULE=1 -I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
> -I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
> -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD  -E
> -D__GENKSYMS__ mixer_oss.c
> 
> - it sems to be OK at this point.
> 
> But then:
> 
> gcc -M -D__KERNEL__ -DMODULE=1
> -I/home/tom/devel/aeg/ALSA/cvs/alsa-driver/include
> -I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
> -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
> gus_dma.c gus_dram.c gus_instr.c gus_io.c gus_irq.c gus_lfo.c gus_main.c
> gus_mem.c gus_mem_proc.c gus_mixer.c gus_pcm.c gus_reset.c gus_sample.c
> gus_simple.c gus_synth.c gus_timer.c gus_uart.c gus_volume.c gusclassic.c
> gusextreme.c gusmax.c interwave-stb.c interwave.c > .depend
> make[3]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/isa/gus'
> make  -C msnd fastdep
> make: Entering an unknown directory
> make: *** msnd: No such file or directory.  Stop.
> make: Leaving an unknown directory
> make[2]: *** [_sfdep_msnd] Error 2
> make[2]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver/isa'
> make[1]: *** [dep] Error 1
> make[1]: Leaving directory `/home/tom/devel/aeg/ALSA/cvs/alsa-driver'
> make: *** [include/sndversions.h] Error 2
> tom@PC18:~/devel/aeg/ALSA/cvs/alsa-driver$ 
> 
> 
> What is the "true one" method of compling ALSA CVS?
> 

It's in the online docs but for your convienience

./cvscompile --with-cards=snd-xxx;make;make install

where snd-xxx is the name of the module for your card.


-- 
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[James Tappin]

On Wed, 23 Oct 2002 19:51:39 +0900
Patrick Shirkey <pshirkey@boosthardware.com> wrote:

PS> > 
PS> > What is the "true one" method of compling ALSA CVS?
PS> > 
PS> 
PS> It's in the online docs but for your convienience
PS> 
PS> ./cvscompile --with-cards=snd-xxx;make;make install
PS> 
PS> where snd-xxx is the name of the module for your card.
PS> 

nearly:
./cvscompile --with-cards=xxx;make;make install
where snd-xxx is the name of the module for your card.

James
-- 
+------------------------+-------------------------------+---------+
| James Tappin           | School of Physics & Astronomy |  O__    |
| sjt@star.sr.bham.ac.uk | University of Birmingham      | --  \/` |
| Ph: 0121-414-6462. Fax: 0121-414-3722                  |         |
+--------------------------------------------------------+---------+


-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[Takashi Iwai]

At Wed, 23 Oct 2002 12:37:10 +0200 (CEST),
tomasz motylewski wrote:
> 
> 
> I have just updated to CVS.
> 
> Debian 2.2
> 
> I needed to run autoconf; ./configure; make; ./configure; make

do you mean that the original configure script in rc4 tarball doesn't
work?  if yes, it's a bug of rc4 tarball - we have to release rc5...


Takashi


-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[m]

 
> nearly:
> ./cvscompile --with-cards=xxx;make;make install
> where snd-xxx is the name of the module for your card.

i had errors running ./cvscompile and also with running the configure
script that comes with the CVS download, or manually running make
ALSAKERNELDIR=../alsa-kernel... 

last night's rc4 release is fine though.

bw
m

-- 
iriXx
www.iriXx.org

copyleft: creativity, technology and freedom?
info@copyleftmedia.org.uk
www.copyleftmedia.org.uk

 _
( )  ascii ribbon against html email
 X
/ \    cat /dev/sda1 > /dev/dsp


  *** stopping make sense ***



-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[Takashi Iwai]

At Wed, 23 Oct 2002 12:24:41 +0100,
James Tappin wrote:
> 
> On Wed, 23 Oct 2002 19:51:39 +0900
> Patrick Shirkey <pshirkey@boosthardware.com> wrote:
> 
> PS> > 
> PS> > What is the "true one" method of compling ALSA CVS?
> PS> > 
> PS> 
> PS> It's in the online docs but for your convienience
> PS> 
> PS> ./cvscompile --with-cards=snd-xxx;make;make install
> PS> 
> PS> where snd-xxx is the name of the module for your card.
> PS> 
> 
> nearly:
> ./cvscompile --with-cards=xxx;make;make install

well, more nearly :)

./cvscompile --with-cards=xxx; make install

you don't have to call make, because cvscompile already runs make by
itself.


Takashi


-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[tomasz motylewski]

On Wed, 23 Oct 2002, Takashi Iwai wrote:

> > I have just updated to CVS.
> > 
> > Debian 2.2
> > 
> > I needed to run autoconf; ./configure; make; ./configure; make
> 
> do you mean that the original configure script in rc4 tarball doesn't
> work?  if yes, it's a bug of rc4 tarball - we have to release rc5...

No, I have got CVS version, but did not run cvscompile - my fault.

But now with the real rc4  tarball and 2.4.9 kernel + Debian 2.2rev7
./configure
make
[...]
make[3]: Leaving directory `/tmp/alsa-driver-0.9.0rc4/isa/wavefront'
/tmp/alsa-driver-0.9.0rc4/include/sndversions.h was not updated
gcc -M -D__KERNEL__ -DMODULE=1 -I/tmp/alsa-driver-0.9.0rc4/include
-I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
-DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
als100.c azt2320.c cmi8330.c dt019x.c es18xx.c opl3sa2.c sgalaxy.c sscape.c >
.depend
sscape.c:500: macro `min' used with only 2 args
make[2]: *** [fastdep] Error 1
make[2]: Leaving directory `/tmp/alsa-driver-0.9.0rc4/isa'
make[1]: *** [dep] Error 1
make[1]: Leaving directory `/tmp/alsa-driver-0.9.0rc4'
make: *** [include/sndversions.h] Error 2


I would say, low priority - 2.4.9 kernel is probably quite exotic at the
moment.

alsa-driver-0.9.0rc4 compiles OK on Debian-3.0 with 2.4.20pre8 kernel.

Best regards,
--
Tomek



-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en

Re: rc4

[Takashi Iwai]

At Wed, 23 Oct 2002 20:17:15 +0200 (CEST),
tomasz motylewski wrote:
> 
> On Wed, 23 Oct 2002, Takashi Iwai wrote:
> 
> > > I have just updated to CVS.
> > > 
> > > Debian 2.2
> > > 
> > > I needed to run autoconf; ./configure; make; ./configure; make
> > 
> > do you mean that the original configure script in rc4 tarball doesn't
> > work?  if yes, it's a bug of rc4 tarball - we have to release rc5...
> 
> No, I have got CVS version, but did not run cvscompile - my fault.
> 
> But now with the real rc4  tarball and 2.4.9 kernel + Debian 2.2rev7
> ./configure
> make
> [...]
> make[3]: Leaving directory `/tmp/alsa-driver-0.9.0rc4/isa/wavefront'
> /tmp/alsa-driver-0.9.0rc4/include/sndversions.h was not updated
> gcc -M -D__KERNEL__ -DMODULE=1 -I/tmp/alsa-driver-0.9.0rc4/include
> -I/lib/modules/2.4.9/build/include -O2 -mpreferred-stack-boundary=2 -march=i686
> -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -DALSA_BUILD
> als100.c azt2320.c cmi8330.c dt019x.c es18xx.c opl3sa2.c sgalaxy.c sscape.c >
> .depend
> sscape.c:500: macro `min' used with only 2 args
> make[2]: *** [fastdep] Error 1
> make[2]: Leaving directory `/tmp/alsa-driver-0.9.0rc4/isa'
> make[1]: *** [dep] Error 1
> make[1]: Leaving directory `/tmp/alsa-driver-0.9.0rc4'
> make: *** [include/sndversions.h] Error 2
> 
> 
> I would say, low priority - 2.4.9 kernel is probably quite exotic at the
> moment.

yes, i guess it's the kernel version problem.
there was the time shortly once that min() and max() macro takes the
third argument for specifying the variable type.  it was removed in
the later version.

there are definitions of correct min() and max() macros in adriver.h.
they are protected by ifdef, so you can put

#undef min

and

#undef max

so that they will be redefined.
i hope this doesn't conflict...


Takashi


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote