Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001351]: The misc.c is reported to have incomplete type with thread_excited.
Date: Fri, 23 Sep 2005 08:57:02 +0200	[thread overview]
Message-ID: <da18d3963620f792f9a315d9647a2c37@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1351> 
======================================================================
Reported By:                lionhead
Assigned To:                perex
======================================================================
Project:                    ALSA - driver
Issue ID:                   1351
Category:                   0_compilation problem_!!!
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Distribution:               the structure description of thread_excited in
acore/misc.c caused failure during compilation.
Kernel Version:             linux-2.4.7-10
======================================================================
Date Submitted:             08-21-2005 12:32 CEST
Last Modified:              09-23-2005 08:57 CEST
======================================================================
Summary:                    The misc.c is reported to have incomplete type with
thread_excited.
Description: 
kernel :linux-2.4.7-10. 
When I compile the alsa drive on my redhat7.2, it always failed with
result as below.

results:
------------------------------------------------------------------------------
[/home/ws/sound/alsa-driver-1.0.9rc4a]$ make
make[1]: Entering directory `/home/ws/sound/alsa-driver-1.0.9rc4a/acore'
gcc -D__KERNEL__ -DMODULE=1 -I/home/ws/sound/alsa-driver-1.0.9rc4a/include
 -I/lib/modules/2.4.7-1
0/build/include -O2 -mpreferred-stack-boundary=2 -march=athlon -DLINUX
-Wall -Wstrict-prototypes -
fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-pipe -DALSA_BUILD -nostdi
nc -iwithprefix include -DMODVERSIONS -include
/lib/modules/2.4.7-10/build/include/linux/modversio
ns.h  -DKBUILD_BASENAME=misc   -c -o misc.o misc.c
misc.c:289: field `thread_exited' has incomplete type <--------- 
misc.c: In function `snd_compat_destroy_workqueue_Raba0304c':
misc.c:340: warning: implicit declaration of function
`wait_for_completion_R02032293'
misc.c: In function `snd_compat_create_workqueue_R6659e20e':
misc.c:388: warning: implicit declaration of function `init_completion'
-------------------------------------------------------------------------------
======================================================================

----------------------------------------------------------------------
 perex - 08-22-05 12:21 
----------------------------------------------------------------------
Could you retest with 1.0.10rc1?

----------------------------------------------------------------------
 croiset - 09-23-05 08:57 
----------------------------------------------------------------------
I also reproduce the problem with my configuration redhat 7.2 kernel 2.4.7
in the release 1.0.9.

I test also the new release 1.0.10rc1 and the problem still exist also :
misc.c:289: field `thread_exited' has incomplete type
misc.c: In function `snd_compat_destroy_workqueue_Raba0304c':
misc.c:340: warning: implicit declaration of function
`wait_for_completion_R020
32293'
misc.c: In function `snd_compat_create_workqueue_R6659e20e':
misc.c:388: warning: implicit declaration of function `init_completion'
make[1]: *** [misc.o] Erreur 1

Issue History
Date Modified  Username       Field                    Change              
======================================================================
08-21-05 12:32 lionhead       New Issue                                    
08-21-05 12:32 lionhead       File Added: misc.c                           
08-21-05 12:32 lionhead       Distribution              => the structure
description of thread_excited in acore/misc.c caused failure during compilation.
08-21-05 12:32 lionhead       Kernel Version            => linux-2.4.7-10  
08-22-05 12:21 perex          Note Added: 0005891                          
08-22-05 12:31 perex          Status                   assigned => feedback
08-22-05 12:31 perex          Steps to Reproduce Updated                    
08-29-05 14:54 lionhead       Issue Monitored: lionhead                    
09-23-05 08:57 croiset        Note Added: 0006362                          
======================================================================




-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php

             reply	other threads:[~2005-09-23  6:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23  6:57 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-14  9:21 [ALSA - driver 0001351]: The misc.c is reported to have incomplete type with thread_excited bugtrack
2005-09-23 10:25 bugtrack
2005-08-22 10:31 bugtrack
2005-08-22 10:21 bugtrack
2005-08-21 10:32 bugtrack

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=da18d3963620f792f9a315d9647a2c37@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /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