Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ivica Bukvic" <ico@fuse.net>
To: 'Paul Davis' <pbd@op.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: RE: Failed to compile HDSP driver from the CVS
Date: Tue, 14 May 2002 21:31:08 -0400	[thread overview]
Message-ID: <000001c1fbb0$32eb45a0$ac1f830a@ico> (raw)
In-Reply-To: <200205150001.g4F012T12698@post2.fast.net>

> -----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

  parent reply	other threads:[~2002-05-15  1:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14 22:16 Failed to compile HDSP driver from the CVS Ivica Bukvic
2002-05-15  0:02 ` Paul Davis
2002-05-15  1:18   ` unresolved symbols, cvs, hammerfall Fernando Pablo Lopez-Lezcano
2002-05-15  1:31   ` Ivica Bukvic [this message]
2002-05-15  1:39   ` Failed to compile HDSP driver from the CVS -- solution? Ivica Bukvic
2002-05-15  2:11   ` HDSP -- how to configure modules.conf? Ivica Bukvic
2002-05-15 12:41     ` Paul Davis
2002-05-15 17:22       ` Ivica Bukvic
2002-05-15 17:27         ` Paul Davis
  -- strict thread matches above, loose matches on Subject: below --
2002-05-14 22:19 Failed to compile HDSP driver from the CVS Ivica Bukvic
2002-05-14  6:51 Ivica Bukvic
2002-05-14 13:07 ` Paul Davis
2002-05-14 13:30   ` Ivica Bukvic
2002-05-14 13:58     ` Paul Davis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000001c1fbb0$32eb45a0$ac1f830a@ico' \
    --to=ico@fuse.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@op.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox