On Tue, 2005-02-01 at 23:20 +, Roger Leigh wrote:
Nope, I've been using a pristine upstream source.
Why isn't the documentation available pre-generated in the upstream
source? If upstream are using gtk-doc correctly, this should be
automatic.
Because upstream author didn't want to
On Tue, 2005-02-01 at 20:48 +, Roger Leigh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Roger Leigh [EMAIL PROTECTED] writes:
Also, it's typical for gtk-doc-using packages to always distribute
their documentation, so it's unusual a doc rebuild is happening. Have
you
On Tue, 2005-02-01 at 19:26 +, Roger Leigh wrote:
Scan failed
make[3]: *** [scan-build.stamp] Error 255
make[3]: Leaving directory `/build/buildd/kipina-0.1.1/doc/reference'
But this scan failed thing is not reproducible on i386 (also it is not
on powerpc).
That's a problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Moreno Garza [EMAIL PROTECTED] writes:
On Tue, 2005-02-01 at 19:26 +, Roger Leigh wrote:
Scan failed
make[3]: *** [scan-build.stamp] Error 255
make[3]: Leaving directory `/build/buildd/kipina-0.1.1/doc/reference'
But this scan
Hello,
Could you please provide a reproducible test?
I have a similar issue on #291786, but not quite sure if this bug also
could be the cause of that one:
CC=ia64-linux-gcc LD=ia64-linux-gcc CFLAGS=`pkg-config --cflags gtk
+-2.0 glib-2.0 libxml-2.0 libxslt libglade-2.0` -I../../src
5 matches
Mail list logo
