GNOME Bugzilla – Bug 302231
Libwnck CVS HEAD fails to compile w/ --enable-gtk-doc
Last modified: 2005-07-19 04:04:27 UTC
Version details: CVS HEAD The error below occours when Libwnck directory from CVS is processed for the very first time. Once you re-enter the directory again or re-run the buildscript the entire module compiles and installs properly. But though it should build from beginning without getting this error. Someone please fix. ---------------------------------------------- cd . && \ gtkdoc-scan --module=libwnck --source-dir=../libwnck --ignore-headers="" touch scan-build.stamp *** Rebuilding template files *** cd . && gtkdoc-mktmpl --module=libwnck ============================================================================= WARNING: 20 unused declarations. These can be found in libwnck-unused.txt. They should be added to libwnck-sections.txt in the appropriate place. ============================================================================= touch tmpl-build.stamp make[2]: *** No rule to make target `tmpl/*.sgml', needed by `sgml-build.stamp'. Stop. make[2]: Leaving directory `/mnt/gnome/libwnck/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mnt/gnome/libwnck' make: *** [all] Error 2
I did 'rm -rf libwnck; jhbuild buildone -ac libwnck' and that built with no problems here. Are you passing any flags to autogen.sh?
There is no need to explicitly mention JHBuild in every conversation we have because it's not the problem I was reporting, not the solution and of course you know that I'm using CVSGnome for the past couple of years now (since the day I wrote it). As a throughly skilled person, when I look at above report then I see plenty of things. a) gtk-doc comes into my mind b) the failure happens in the doc section c) sgml Sounds like I was trying to build the reference manual and that usually requires a --enable-gtk-doc by default. The gtk-doc build process has been reversed in the past 2 years or so. Initially the reference manuals got build and if you don't want this then you had to pass --disable-gtk-doc to the autogen.sh or configure scripts but nowadays if you want the reference manuals to get build you need to --enable-gtk-doc to explicitly tell it to do so. Now catch your ultimate build solution and append --enable-gtk-doc to it and repeat the steps you mentioned above starting with a rm -rf libwnck which of course sounds very reasonable to me. It's necessary for the quality assurance team and release management to 'throughly' test the things before releasign it and of course every individual should give the CVS a try building it a) normally and b) trying to build the same stuff again with reference manuals, since these are two entire build processes. People usually avoid messing with the reference manuals because only a handful of people seem to have the balls to handle docbook stuff correctly. Hope my throughly explaination was helpful solving this problem.
Yep. I can reproduce this now. I wrongly assumed all modules built api reference manuals when built from CVS.
Any progress with this ?
2005-07-19 Matthias Clasen <mclasen@redhat.com> * doc/tmpl/*.sgml: Add template files to cvs, to make a clean build from cvs work. (#302231, Ali Akcaagac)