First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 119272
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Java team <java@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Anton Romanov <theli@ukr.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
alsa.patch alsa.patch text/plain Anton Romanov 2006-01-18 00:12 0000 1.16 KB Details
info emerge --info output text/plain Anton Romanov 2006-01-18 00:13 0000 2.31 KB Details
alsa.patch alsa.patch text/plain Anton Romanov 2006-01-18 00:50 0000 1.10 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 119272 depends on: Show dependency tree
Bug 119272 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-01-17 03:38 0000 
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)

------- Comment #1 From Josh Nichols (RETIRED) 2006-01-17 16:21:16 0000 ------- 
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.

------- Comment #2 From Anton Romanov 2006-01-18 00:11:10 0000 ------- 
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.

------- Comment #3 From Anton Romanov 2006-01-18 00:12:45 0000 ------- 
Created an attachment (id=77398) [edit]
alsa.patch

and upstream already knew about the problem before your message :) ... just
about 5 posts before yours

------- Comment #4 From Anton Romanov 2006-01-18 00:13:14 0000 ------- 
Created an attachment (id=77399) [edit]
emerge --info output

------- Comment #5 From Anton Romanov 2006-01-18 00:50:53 0000 ------- 
Created an attachment (id=77403) [edit]
alsa.patch

------- Comment #6 From Josh Nichols (RETIRED) 2006-01-19 21:32:52 0000 ------- 
Fixed with 1.1.6-r2. Thanks for reporting!

------- Comment #7 From Jakub Moc (RETIRED) 2006-06-03 00:49:56 0000 ------- 
*** Bug 135342 has been marked as a duplicate of this bug. ***

------- Comment #8 From sharpshopter@gmail.com 2006-06-03 00:58:38 0000 ------- 
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.

------- Comment #9 From Petteri Räty 2006-06-24 05:53:26 0000 ------- 
(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.

------- Comment #10 From Jakub Moc (RETIRED) 2006-07-05 00:48:18 0000 ------- 
*** Bug 139264 has been marked as a duplicate of this bug. ***
First Last Prev Next    No search results available      Search page      Enter new bug