Bug 27332 - compilation of alsa_a.cpp fails because of unallowed typecasts
Summary: compilation of alsa_a.cpp fails because of unallowed typecasts
Status: RESOLVED DUPLICATE of bug 39574
Alias: None
Product: kmidi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Bernd Wuebben
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-16 22:03 UTC by F Bachmann
Modified: 2003-07-06 06:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description F Bachmann 2001-06-16 21:51:58 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kmidi
Version:           KDE 2.2.0 CVS/CVSup/Snapshot
Severity:          normal
Installed from:    Compiled sources
Compiler:          gcc 2.95.3
OS:                Linux
OS/Compiler notes: alsa-0.5.11

For some time now compilation of kmidi fails due to some unallowed typecasts... This is really trivial to fix though.

In alsa_a.cpp the "__handle" argument used in the snd_... calls is declared as void* and must be casted to snd_pcm_t*.



(Submitted via bugs.kde.org)
Comment 1 Ken Zalewski 2001-09-23 09:40:33 UTC
This bug was reported against 2.2.0.  It is still existing in 2.2.1.

The fix is simply to change the function declaration on line 257 of 
alsa_a.cpp from:

static int set_playback_info (void* handle__ .......  )

to:

static int set_playback_info (snd_pcm_t* handle__ ....... )


This 30-second change should not slip through the next bugfix release of KDE.
Comment 2 Berni Elbourn 2002-03-06 21:51:42 UTC
....might be worth puttting the fix in the INSTALL file.

Berni
Comment 3 Russell Miller 2003-07-03 19:51:01 UTC
Has this change slipped through the next bugfix release of KDE?  If so, I apologize. 
 
--Russell 
Comment 4 Russell Miller 2003-07-06 06:53:47 UTC
Please follow #39574 to track additional progress on this bug, as the action taken to 
resolve that bug will also solve this bug. 

*** This bug has been marked as a duplicate of 39574 ***