Re: Failed to compile HDSP driver from the CVS

Re: Failed to compile HDSP driver from the CVS

[Ivica Bukvic]

Apologies if this thing got posted twice. My mail has been acting up
lately.

I am a bit confused. It is not the fact that I do have this file, but
that the compile was looking for it. It must have been that issue you
mentioned about CVS being not up-to-date. However, here's the error when
I try to compile the driver now, after updating it with 

cvs -z3 -d ':pserver:anonymous@cvs.alsa-project.org:/cvsroot/alsa'
update -P -d 

I get the following error: 

make[3]: Leaving directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/pdplus' 
make  -C rme9652 modules 
make[3]: Entering directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652' 
gcc -DALSA_BUILD -D__KERNEL__ -DMODULE=1
-I/LocalDump/Install/Alsa/CVS/alsa-driver/include
-I/lib/modules/2.4.8-26mdk/build/include -O2
-mpreferred-stack-boundary=2 -march=i586 -DLINUX -Wall
-Wstrict-prototypes -fomit-frame-pointer -pipe   -DEXPORT_SYMTAB -c
hammerfall_mem.c 
In file included from hammerfall_mem.c:1: 
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: parse error before
string constant 
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: type
defaults to `int' in declaration of `MODULE_LICENSE' 
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: function
declaration isn't a prototype 
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: data
definition has no type or storage class 
make[3]: *** [hammerfall_mem.o] Error 1 
make[3]: Leaving directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652' 
make[2]: *** [_modsubdir_rme9652] Error 2 
make[2]: Leaving directory `/LocalDump/Install/Alsa/CVS/alsa-driver/pci'
make[1]: *** [compile] Error 1 
make[1]: Leaving directory `/LocalDump/Install/Alsa/CVS/alsa-driver' 
make: *** [build] Error 2 

Any help is greatly appreciated! 

Sincerely, 

Ico 




_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

Re: Failed to compile HDSP driver from the CVS

[Paul Davis]

>I am a bit confused. It is not the fact that I do have this file, but
>that the compile was looking for it. It must have been that issue you
>mentioned about CVS being not up-to-date. 

its a combination of the "fastdep" target looking at *all* existing
sources, whether they are meant to be there or not, plus the CVS sync issue.

					   However, here's the error when
>I try to compile the driver now, after updating it with 

use cvscompile to build it, i think.

--p


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

unresolved symbols, cvs, hammerfall

[Fernando Pablo Lopez-Lezcano]

Just downloaded from cvs, I'm getting this unresolved symbols:

# depmod -a -e
depmod: *** Unresolved symbols in  
/lib/modules/2.4.18-2.ll/kernel/drivers/sound/pci/rme9652/snd-hammerfall-mem.o
depmod: 	pci_free_consistent
depmod: 	pci_alloc_consistent
depmod: 	pci_devices
depmod: 	mem_map
depmod: 	printk
depmod: *** Unresolved symbols in  
/lib/modules/2.4.18-2.ll/kernel/drivers/sound/pci/rme9652/snd-rme9652.o
depmod: 	snd_hammerfall_get_buffer_R511cb671
depmod: 	snd_hammerfall_free_buffer_R4a11134f

Maybe something's missing in the recent Hammerfall updates?
This is being compiled under 2.4.18 + 19-pre7 + low latency,
full sources for the kernel are properly installed.

-- Fernando

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

RE: Failed to compile HDSP driver from the CVS

[Ivica Bukvic]

> -----Original Message-----
> From: Paul Davis [mailto:pbd@op.net]
> Sent: Tuesday, May 14, 2002 8:02 PM
> To: Ivica Bukvic
> Cc: alsa-devel@lists.sourceforge.net
> Subject: Re: Failed to compile HDSP driver from the CVS
> 
> >I am a bit confused. It is not the fact that I do have this file, but
> >that the compile was looking for it. It must have been that issue you
> >mentioned about CVS being not up-to-date.
> 
> its a combination of the "fastdep" target looking at *all* existing
> sources, whether they are meant to be there or not, plus the CVS sync
> issue.
> 
> 					   However, here's the error
when
> >I try to compile the driver now, after updating it with
> 
> use cvscompile to build it, i think.
> 
> --p

But all this still comes up with the same error, so this does not seem
to be the solution. The compiling still stops with the same error which
I am unable to figure out since it has to do with some define statements
at the beginning of the hammerfall_mem.c file:

make  -C rme9652 modules
make[2]: Entering directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652'
gcc -DALSA_BUILD -D__KERNEL__ -DMODULE=1
-I/LocalDump/Install/Alsa/CVS/alsa-driver/include
-I/lib/modules/2.4.8-26mdk/build/include -O2
-mpreferred-stack-boundary=2 -march=i586 -DLINUX -Wall
-Wstrict-prototypes -fomit-frame-pointer -pipe   -DEXPORT_SYMTAB -c
hammerfall_mem.c
In file included from hammerfall_mem.c:1:
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: parse error before
string constant
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: type
defaults to `int' in declaration of `MODULE_LICENSE'
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: function
declaration isn't a prototype
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: data
definition has no type or storage class
make[2]: *** [hammerfall_mem.o] Error 1
make[2]: Leaving directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652'
make[1]: *** [_modsubdir_rme9652] Error 2
make[1]: Leaving directory `/LocalDump/Install/Alsa/CVS/alsa-driver/pci'
make: *** [compile] Error 1

It is obvious that it is having a problem with the hammerfall_mem.c
file, not the addition or removal of rme9652_mem.c file any more.

Does anyone else seem to have a problem with this one or is it just me?

Ico



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

RE: Failed to compile HDSP driver from the CVS -- solution?

[Ivica Bukvic]

Hmmm, when I comment out the line 58 in the hammerfall_mem.c which says

MODULE_LICENSE("GPL");

Then everything compiles fine.

?

Ico




_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

HDSP -- how to configure modules.conf?

[Ivica Bukvic]

Sorry Paul for cluttering your inbox :-(

Just a quick question:

Do I use snd-rme9652.o module for hdsp or which one?

Obviously, I also need to modprobe snd-hammerfall-mem.o.

Could you please just post your example of the modules.conf for this
beast so that I know for sure that there are no extra flags I need to
worry about.

Thanks a lot!

Ico




_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

Re: HDSP -- how to configure modules.conf?

[Paul Davis]

>Sorry Paul for cluttering your inbox :-(
>
>Just a quick question:
>
>Do I use snd-rme9652.o module for hdsp or which one?

snd-hdsp.o

>Obviously, I also need to modprobe snd-hammerfall-mem.o.

yes, and almost certainly early in the boot sequence. i use
/etc/rc.d/rc.sysinit, and do it before running fsck.

>Could you please just post your example of the modules.conf for this
>beast so that I know for sure that there are no extra flags I need to
>worry about.

this is the audio-related section. the only option you need worry
about is the snd-enable option to snd-hammerfall-mem.o, and even that
is optional because by default the module will just allocate memory
for every Hammerfall or Hammerfall DSP device that it finds.

--p

----------------------------------------------------------------------
# Audio

# soundcore is the multiplexer for any and all sound drivers
# and ALSA hangs from major device 116

alias char-major-14 soundcore
alias char-major-116 snd

# soundcore/OSS service number notes:
# 0: /dev/mixer
# 1: /dev/sequencer
# 2: /dev/midi
# 3: /dev/dsp
# 4: /dev/audio
# 5: /dev/dspW
# 6: sndstat
# 8: /dev/music
# 9: /dev/synth
# 10: /dev/dmfm
# 12: /dev/adsp

# Four soundcards. 
# OSS-style opens look for sound-slot-N
# ALSA-style opens look for snd-card-N

alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
alias sound-slot-2 snd-card-2
alias sound-slot-3 snd-card-3

alias snd-card-0 snd-wavefront
alias snd-card-1 snd-trident
alias snd-card-2 snd-rme9652
alias snd-card-3 snd-hdsp

# First soundcard is a Turtle Beach Tropez+, which has a CS4232 (with
# an ad1848 CODEC), the usual OPL3, and an ICS2115 wavetable
# synthesizer with its own MIDI interface.  

# Here, we leave the CS4232 MIDI interface undefined, since it uses a
# physical interface that is only accessible from within the case of
# the machine and I'm not interested in using it. To use it, set:
#
#	snd_cs4232_mpu_port
#	snd_cs4232_mpu_irq

options snd-wavefront snd_id="Tropez+"
options snd-wavefront-synth \
	reset_time=100 \
	debug_default=0xffff \
	wf_raw=1

alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-12 snd-pcm-oss

# Second soundcard is HoonTech SoundWave 4D-NX, based on
# the Trident 4D-NX chip. 

options snd-trident snd_id="4D"

alias sound-service-1-0  snd-mixer-oss
alias sound-service-1-3  snd-pcm-oss
alias sound-service-1-12 snd-pcm-oss

# Both the RME9652 and Hammerfall DSP drivers use
# the snd-hammerfall_mem module.

options snd-hammerfall_mem snd_enable=1,1

# Third card is an RME Digi9652 (Hammerfall)
# It offers nothing but pure digital PCM 

options snd-rme9652 snd_id="9652"

# Fourth card is an RME Hammerfall DSP card
# It offers variety of things

options snd-hdsp snd_id="hdsp"

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

RE: HDSP -- how to configure modules.conf?

[Ivica Bukvic]

> >Do I use snd-rme9652.o module for hdsp or which one?
> 
> snd-hdsp.o

Problem is there is no such module that gets compiled. Tried compiling
on two different boxes with multiple CVS updates and complete nukes.

After installing the whole thing, in the alsa-driver/modules/ there is
no such module, nor in the /lib/modules/...

Again, has anyone else tried compiling the driver from the CVS and had a
success?

Ico



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

Re: HDSP -- how to configure modules.conf?

[Paul Davis]

>> >Do I use snd-rme9652.o module for hdsp or which one?
>> 
>> snd-hdsp.o
>
>Problem is there is no such module that gets compiled. Tried compiling
>on two different boxes with multiple CVS updates and complete nukes.
>
>After installing the whole thing, in the alsa-driver/modules/ there is
>no such module, nor in the /lib/modules/...
>
>Again, has anyone else tried compiling the driver from the CVS and had a
>success?

How did you compile? I mean right from the very beginning ... I've
obviously been building from CVS all along, and I assume that Jaroslav
did a rebuild after he committed the changes.

--p

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

Re: Failed to compile HDSP driver from the CVS

[Ivica Bukvic]

Also, there is a build shell script in the root dir of the CVS. Is it
better to use that or just type make (I tried both ways with same
results)

Ico



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

Failed to compile HDSP driver from the CVS

[Ivica Bukvic]

Hi all!

First off, thank you very much for the awesome news Paul, I am extatic
to hear that HDSP driver is ready! :-)

However, I've been trying to compile it from the CVS and no matter what
I try I get the same error:

<snip>

make  -C rme9652 fastdep
make[2]: Entering directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652'
/LocalDump/Install/Alsa/CVS/alsa-driver/include/sndversions.h was not
updated
gcc -DALSA_BUILD -D__KERNEL__ -DMODULE=1
-I/LocalDump/Install/Alsa/CVS/alsa-driver/include
-I/lib/modules/2.4.8-26mdk/build/include -O2
-mpreferred-stack-boundary=2 -march=i586 -DLINUX -Wall
-Wstrict-prototypes -fomit-frame-pointer -pipe  -E -D__GENKSYMS__
hammerfall_mem.c
| /sbin/genksyms -k 2.4.8  >
/LocalDump/Install/Alsa/CVS/alsa-driver/include/modules/pci-rme9652__hammerfall_mem.ver.tmp
mv
/LocalDump/Install/Alsa/CVS/alsa-driver/include/modules/pci-rme9652__hammerfall_mem.ver.tmp /LocalDump/Install/Alsa/CVS/alsa-driver/include/modules/pci-rme9652__hammerfall_mem.ver
gcc -E -M -DALSA_BUILD -D__KERNEL__ -DMODULE=1
-I/LocalDump/Install/Alsa/CVS/alsa-driver/include
-I/lib/modules/2.4.8-26mdk/build/include -O2
-mpreferred-stack-boundary=2 -march=i586 -DLINUX -Wall
-Wstrict-prototypes -fomit-frame-pointer -pipe  hammerfall_mem.c hdsp.c
rme9652.c rme9652_mem.c > .depend
In file included from ../../alsa-kernel/pci/rme9652/hdsp.c:38,
                 from hdsp.c:1:
../../alsa-kernel/pci/rme9652/digiface_firmware.dat:4884:26: warning: no
newline at end of file
rme9652_mem.c:45:55: ../../alsa-kernel/pci/rme9652/rme9652_mem.c: No
such file or directory make[2]: *** [fastdep] Error 1
make[2]: Leaving directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652'
make[1]: *** [_sfdep_rme9652] Error 2
make[1]: Leaving directory `/LocalDump/Install/Alsa/CVS/alsa-driver/pci'
make: *** [dep] Error 1

I am not sure what this means, since there is no rme9652_mem.c file at
all in the alsa-kernel/pci/rme9652/ folder. Is this the way it's
supposed to be?

I tried soft-linking the rme9652_mem.c to hammerfall_mem.c without
success. I also tried copying the older driver's rme9652_mem.c into the
same folder. But, that gives me a different error:

make  -C rme9652 modules
make[3]: Entering directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652'
gcc -DALSA_BUILD -D__KERNEL__ -DMODULE=1
-I/LocalDump/Install/Alsa/CVS/alsa-driver/include
-I/lib/modules/2.4.8-26mdk/build/include -O2
-mpreferred-stack-boundary=2 -march=i586 -DLINUX -Wall
-Wstrict-prototypes -fomit-frame-pointer -pipe   -DEXPORT_SYMTAB -c
hammerfall_mem.c In file included from hammerfall_mem.c:1:
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: parse error before
string constant
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: type
defaults to `int' in declaration of `MODULE_LICENSE'
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: function
declaration isn't a prototype
../../alsa-kernel/pci/rme9652/hammerfall_mem.c:58: warning: data
definition has no type or storage class
make[3]: *** [hammerfall_mem.o] Error 1
make[3]: Leaving directory
`/LocalDump/Install/Alsa/CVS/alsa-driver/pci/rme9652'
make[2]: *** [_modsubdir_rme9652] Error 2
make[2]: Leaving directory `/LocalDump/Install/Alsa/CVS/alsa-driver/pci'
make[1]: *** [compile] Error 1
make[1]: Leaving directory `/LocalDump/Install/Alsa/CVS/alsa-driver'
make: *** [build] Error 2

Any insight into this one would be utmostly appreciated.

BTW, I am using MDK 8.1 (modified somewhat) and I just noticed that
there is still some rpm junk lingering around from the 0.5.11 version
that shipped with the MDK (even though I've been using the 0.9 version
for a while now and 0.5 seemed not to bother 0.9).

Finally, the question regarding the CVS compiling:

Do I still need to specify the --have-sequencer=yes flag or is this now
being done automatically?

Thank you for your help! Sincerely,

Ico




_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

Re: Failed to compile HDSP driver from the CVS

[Paul Davis]

>First off, thank you very much for the awesome news Paul, I am extatic
>to hear that HDSP driver is ready! :-)
>
>However, I've been trying to compile it from the CVS and no matter what
>I try I get the same error:

i think you failed to use the "-P" flag to the CVS update
command. Always use this flag, otherwise when someone removes a file
from CVS, its not removed from your local tree. 

as a result, you've still got rme9652_mem.c hanging around, and the
"fastdep" make target looks at *all* sources, not just those that are
listed in the Makefile. you need to remove this file. there are two
versions of it, one under alsa-kernel, one under alsa-driver.

please keep in mind that you should update alsa-lib and alsa-utils as
well, because they have been modified to support the 64 bit register
used by the H-DSP for its RMS meters.

--p

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

RE: Failed to compile HDSP driver from the CVS

[Ivica Bukvic]

Thank you for your prompt reply!

However, this is the first time ever I tried using the CVS, so I had no
files hanging around prior to this downloading. I am also pretty sure
that I downloaded the stuff with -P flag (I did it as instructions on
the alsa-project page have stated it, including the -P flag). On top of
that I even tried updating the whole CVS tree just to see if that will
fix it.

So, I am not sure why it is even referencing the file in the first place
if none of the other files are supposed to mention it.

Should I uninstall every trace of Alsa from my cpu before trying to use
CVS?

Ico

> -----Original Message-----
> From: Paul Davis [mailto:pbd@op.net]
> Sent: Tuesday, May 14, 2002 9:07 AM
> To: Ivica Bukvic
> Cc: alsa-devel@alsa-project.org
> Subject: Re: Failed to compile HDSP driver from the CVS

> i think you failed to use the "-P" flag to the CVS update
> command. Always use this flag, otherwise when someone removes a file
> from CVS, its not removed from your local tree.
> 
> as a result, you've still got rme9652_mem.c hanging around, and the
> "fastdep" make target looks at *all* sources, not just those that are
> listed in the Makefile. you need to remove this file. there are two
> versions of it, one under alsa-kernel, one under alsa-driver.
> 
> please keep in mind that you should update alsa-lib and alsa-utils as
> well, because they have been modified to support the 64 bit register
> used by the H-DSP for its RMS meters.
> 
> --p



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

Re: Failed to compile HDSP driver from the CVS

[Paul Davis]

>Thank you for your prompt reply!
>
>However, this is the first time ever I tried using the CVS, so I had no
>files hanging around prior to this downloading. I am also pretty sure
>that I downloaded the stuff with -P flag (I did it as instructions on
>the alsa-project page have stated it, including the -P flag). On top of
>that I even tried updating the whole CVS tree just to see if that will
>fix it.
>
>So, I am not sure why it is even referencing the file in the first place
>if none of the other files are supposed to mention it.
>
>Should I uninstall every trace of Alsa from my cpu before trying to use
>CVS?

No, thats not the issue. It might be a CVS sync issue at sf.net, as
well. The "anonymous" CVS repository is sometimes 6hrs behind the
"login" CVS repository.

rme9652_mem.c is now in the "Attic" meaning that it was removed from
CVS:

pbd[987]>cvs -z3 status rme9652_mem.c
===================================================================
File: no file rme9652_mem.c             Status: Up-to-date

   Working revision:    No entry for rme9652_mem.c
   Repository revision: 1.8     /cvsroot/alsa/alsa-kernel/pci/rme9652/Attic/rme9652_mem.c,v
pbd[988]>

This means that if you checkout ALSA, you should not get this file. I
would suggest that try 
      
 cvs -z3 update -dP

again, and see if that removes the file.

--p

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net