In file included from org_tritonus_lowlevel_alsa_AlsaSeq.c:25: constants_check.h: In function `check_constants': constants_check.h:139: error: `SND_SEQ_CLIENT_DUMMY' undeclared (first use in this function) constants_check.h:139: error: (Each undeclared identifier is reported only once constants_check.h:139: error: for each function it appears in.) constants_check.h:140: error: `SND_SEQ_CLIENT_OSS' undeclared (first use in this function)
When filing bugs, it is customary to include the output of 'emerge info'. This provides little clues about your system, like what platform you are one, what your ACCEPT_KEYWORDS is, USE flags, etc.
commonly i provide this.. but was sure this was unnecessary this time. cause problem is that alsa team removed some constants since >=alsa-lib-1.0.11-rc2... and obviously i try to build kaffe with alsa use flag... anyway.. as you wish.
Created attachment 77398 [details] alsa.patch and upstream already knew about the problem before your message :) ... just about 5 posts before yours
Created attachment 77399 [details] emerge --info output
Created attachment 77403 [details] alsa.patch
Fixed with 1.1.6-r2. Thanks for reporting!
*** Bug 135342 has been marked as a duplicate of this bug. ***
I'm no expert on these things, but should a bug not be marked as resolved until the fix is in the stable branch of portage? As it is now, one tries to emerge the stable kaffe and still gets this error.
(In reply to comment #8) > I'm no expert on these things, but should a bug not be marked as resolved until > the fix is in the stable branch of portage? As it is now, one tries to emerge > the stable kaffe and still gets this error. > I opened a stable request bug for a newer kaffe. See bug #137827.
*** Bug 139264 has been marked as a duplicate of this bug. ***
