First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 144082
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Tim Yamin (RETIRED) <plasmaroo@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Matthias Schwarzott <zzam@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

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

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







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


Description:   Opened: 2006-08-16 01:54 0000
The package media-plugins/vdr-bitstreamout-0.85 fails to compile against
sys-kernel/linux-headers-2.6.17.

>>> Compiling source in /var/tmp/portage/vdr-bitstreamout-0.85/work/bitstreamout-0.85 ...
bitstreamout Version 0.85
g++ -O2 -march=athlon-xp -fomit-frame-pointer -pipe -fPIC -fPIC -DPIC -c
-DCONFIGDIR=\"/etc/vdr\" -DPLUGIN_NAME_I18N='"bitstreamout"' -D_GNU_SOURCE 
-I/usr/include -I/usr/include bitstreamout.c
/usr/include/asm-generic/bitops/fls64.h: In function 'int fls64(__u64)':
/usr/include/asm-generic/bitops/fls64.h:10: error: 'fls' was not declared in
this scope
/usr/include/asm-generic/bitops/fls64.h:11: error: 'fls' was not declared in
this scope
make: *** [bitstreamout.o] Error 1

The function fls which is used by fls64 seems to be defined only for in kernel
usage (#ifdef __KERNEL__). But fls64 is defined without #ifdef around.

vdr-bitstreamout does not use fls/fls64 itself, it only uses some of the other
bitops.

Commenting out the line #include <asm-generic/bitops/fls64.h>
(/usr/include/asm/bitops.h, line #409) or moving it inside the #ifdef
__KERNEL__ block will cure the error for vdr-bitstreamout.

------- Comment #1 From Matthias Schwarzott 2006-09-04 04:39:04 0000 -------
Will this be fixed, or should we think about a workaround?

------- Comment #2 From Tim Yamin (RETIRED) 2006-09-16 05:29:20 0000 -------
(In reply to comment #1)
> Will this be fixed, or should we think about a workaround?

It's now fixed in 2.6.17-r1; sorry for the crazily long delay.

First Last Prev Next    No search results available      Search page      Enter new bug