Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 321421 - media-tv/xbmc-9.11-r4: fails due to ‘UINT64_C’ was not declared in this scope
Summary: media-tv/xbmc-9.11-r4: fails due to ‘UINT64_C’ was not declared in this scope
Status: RESOLVED DUPLICATE of bug 318969
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-25 07:14 UTC by DaggyStyle
Modified: 2010-05-29 05:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
build log (xbmc-build.log,79.49 KB, text/plain)
2010-05-25 07:15 UTC, DaggyStyle 		Details
emerge --info output (emerge.info,4.38 KB, text/plain)
2010-05-25 07:15 UTC, DaggyStyle 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description DaggyStyle 2010-05-25 07:14:36 UTC 
not much to say, maybe caused due to something with libavutil
build log is attached.

Reproducible: Always
Comment 1 DaggyStyle 2010-05-25 07:15:10 UTC 
Created attachment 232843 [details]
build log
Comment 2 DaggyStyle 2010-05-25 07:15:38 UTC 
Created attachment 232845 [details]
emerge --info output
Comment 3 DaggyStyle 2010-05-25 07:18:27 UTC 
the file in question is /usr/include/libavutil/common.h which belongs to ffmpeg.
I'm using ffmpeg from git with the mt patches, can anyone confirm if it is because the patches or because the git files?
Comment 4 hal 2010-05-25 09:18:30 UTC 
(In reply to comment #3)
> the file in question is /usr/include/libavutil/common.h which belongs to
> ffmpeg.
> I'm using ffmpeg from git with the mt patches, can anyone confirm if it is
> because the patches or because the git files?
> 

about 2 weeks ago i tried to compile xbmc against ffmpeg-9999 (svn). it failed to build, but i can't rememeber the file in charge. getting back to a ffmpeg snapshot it worked fine again.
Comment 5 DaggyStyle 2010-05-29 05:58:12 UTC 
found the issue and a workwround

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