Serge,

Your wrote:

> 2) Compiling directly alsa-lib (same version that SFEalsa-lib) with 
> Sunstudio11 (all patches manually applied) :
> 
> "../../include/sound/asound.h", line 165: warning: implicit function 
> declaration: _IOR
> "../../include/sound/asound.h", line 165: syntax error before or at: int
> 
> The problem is here (asound.h) :
> 
> enum {
>       SNDRV_HWDEP_IOCTL_PVERSION = _IOR ('H', 0x00, int),
>       SNDRV_HWDEP_IOCTL_INFO = _IOR ('H', 0x01, struct sndrv_hwdep_info),
>       SNDRV_HWDEP_IOCTL_DSP_STATUS = _IOR('H', 0x02, struct 
> sndrv_hwdep_dsp_status),
>       SNDRV_HWDEP_IOCTL_DSP_LOAD   = _IOW('H', 0x03, struct 
> sndrv_hwdep_dsp_image)
> };
> 
> - with gcc (3 or 4) i get also a "syntax error", without more precision.

When I compile (using SunStudio12) the attached test code with 'cc -c 
testit.c -DNO_IOR'
I get:

bash-3.00$ cc -c testit.c -DNO_IOR
"testit.c", line 12: warning: implicit function declaration: _IOR
"testit.c", line 12: syntax error before or at: int
cc: acomp failed for testit.c
bash-3.00$

Could it be that the asound.h file is being included before the ioccom.h
include?

Or it could be a bug in the compiler.  I'll check the attached code
against an instance of SunStudio11.


Good luck,

John

Serge wrote:
> Hi johnfisc
> 
> Thank's !
> 
> - sys/ioccom.h is already included in asound.h (otherwise it would report 
> about missing declaration, not about syntax error). But your are right : 
> something isn't coherent between the declaration and the usage (alsa-lib 
> comes originally, of course, from Linux). I'll learn that again...
> 
> Cheers,
> 
> Sergio
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testit.c
Type: text/x-csrc
Size: 568 bytes
Desc: not available
URL: 
<http://mail.opensolaris.org/pipermail/desktop-discuss/attachments/20071207/df66419a/attachment.bin>

Reply via email to