I was just trying out the recently added xbmc svn ebuild, and I encounter an error that can easily be fixed by running eautoreconf from within the ebuild. Check out the attachments for build.log and config.log .
Created attachment 182910 [details] build.log
Created attachment 182911 [details] config.log
The problem is that Makefile.include is not auto-generated from Makefile.include.in, even though it is specified in configure.in AC_CONFIG_FILES([Makefile Makefile.include] Running autoreconf from within the source directory fixes the problem. Please see my patch for the ebuild, which includes adding eautoreconf before econf is called.
Created attachment 182912 [details, diff] patch for media-tv/xbmc-9999.ebuild
Created attachment 182978 [details, diff] xbmc-9999-ebuild-conditionally-patch-fribidi-based-on-version.patch In some cases the xbmc-fribidi.patch should not be applied. Namely, when the installed dev-libs/fribidi version < 0.19.1 . This is a patch against the ebuild to patch based on that condition.
Makefile.include is generated by configure based on Makefile.include.in Makefile.include.in is in svn
(In reply to comment #6) > Makefile.include is generated by configure based on Makefile.include.in > > Makefile.include.in is in svn > I would assume so as well, but if you read my build.log, econf was run, and it still complained about a missing Makefile.include . eautoreconf fixed the problem.
no, build.log says it couldnt find "Makefile.include.in" update your svn checkout the xbmc ebuild specifically avoids running autotools
(In reply to comment #8) > no, build.log says it couldnt find "Makefile.include.in" > > update your svn checkout > > the xbmc ebuild specifically avoids running autotools > Jeez ... that's embarrassing. I must have been thrown off by the ^M character. Thanks
maybe there were some ^M gremlins floating in the configure and they fixed it upstream. does it work for you now with latest svn up ?
(In reply to comment #10) > maybe there were some ^M gremlins floating in the configure and they fixed it > upstream. does it work for you now with latest svn up ? > It's good! 7 points!
