After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 386599 - gnome-doc-utils require gnome-doc-utils
gnome-doc-utils require gnome-doc-utils
Status: VERIFIED DUPLICATE of bug 376908
Product: gnome-doc-utils
Classification: Deprecated
Component: build utils
CVS HEAD
Other All
: Normal normal
: ---
Assigned To: gnome-doc-utils maintainers
gnome-doc-utils maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-16 20:44 UTC by Carol
Modified: 2007-01-27 18:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Carol 2006-12-16 20:44:44 UTC
Please describe the problem:
carol@bread:/usr/local/src/gnome/gnome-doc-utils$ ./autogen.sh 
/usr/local/bin/gnome-autogen.sh
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.61
checking for automake >= 1.6...
  testing automake-1.9... found 1.9.6
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.13.0
checking for intltool >= 0.25...
  testing intltoolize... found 0.35.0
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 0.21
checking for gnome-doc-utils >= 0.4.2...
  testing gnome-doc-prepare... not found.
***Error***: You must have gnome-doc-utils >= 0.4.2 installed
  to build gnome-doc-utils.  Download the appropriate package for
  from your distribution or get the source tarball at
    http://ftp.gnome.org/pub/GNOME/sources/gnome-doc-utils/

Checking for required M4 macros...
Checking for forbidden M4 macros...


Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Shaun McCance 2007-01-15 23:29:13 UTC
This is bug #376908, which was fixed a few days ago.

*** This bug has been marked as a duplicate of 376908 ***
Comment 2 Carol 2007-01-27 18:58:33 UTC
All I can really verify is that this bug report has indeed been marked as a duplicate of another.