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 711306 - fails to build because it cannot find the m4 directory
fails to build because it cannot find the m4 directory
Status: RESOLVED FIXED
Product: GConf
Classification: Deprecated
Component: gconf
unspecified
Other Linux
: Normal blocker
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-11-02 19:47 UTC by Venkatesh
Modified: 2013-11-20 15:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fixes build failure (1.04 KB, patch)
2013-11-02 19:50 UTC, Magdalen Berns (irc magpie)
committed Details | Review

Description Venkatesh 2013-11-02 19:47:37 UTC
...
...
...
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking for getuid... yes
checking for sigaction... yes
checking for fsync... yes
checking for fchmod... yes
checking for fdwalk... no
checking ldap.h usability... yes
checking ldap.h presence... yes
checking for ldap.h... yes
checking for ldap_init in -lldap... yes
checking for ber_free in -llber... yes
checking for ldap_ntlm_bind... yes
./configure: line 17326: syntax error near unexpected token `0.35.0'
./configure: line 17326: `IT_PROG_INTLTOOL(0.35.0)'
*** Error during phase configure of gconf: ########## Error running ./autogen.sh --prefix /opt/gnome --libdir '/opt/gnome/lib64' --enable-gtk --with-gtk=3.0 --disable-orbit --disable-static --disable-gtk-doc  *** [53/57]

  [1] Rerun phase configure
  [2] Ignore error and continue to build
  [3] Give up on module
  [4] Start shell
  [5] Reload configuration
  [6] Go to phase "wipe directory and start over"
  [7] Go to phase "clean"
  [8] Go to phase "distclean"
choice: 4
exit shell to continue with build
vicky@ubuntu:~/checkout/gnome/gconf$
Comment 1 Magdalen Berns (irc magpie) 2013-11-02 19:50:55 UTC
Created attachment 258818 [details] [review]
fixes build failure
Comment 2 Venkatesh 2013-11-02 20:07:51 UTC
Magdalen: thank you, your patch works
Comment 3 Colin Walters 2013-11-20 15:29:23 UTC
Review of attachment 258818 [details] [review]:

This is likely to have suddenly become necessary because of gnome-common changes.  

If this patch works for you, I'm ok with it.  But don't we also need to ensure the m4/ directory exists by either:

1) mkdir -p m4 in autogen.sh
2) Adding it in git with an empty .gitignore
Comment 4 Magdalen Berns (irc magpie) 2013-11-20 15:38:40 UTC
Thanks (In reply to comment #3)
> Review of attachment 258818 [details] [review]:
> 
> This is likely to have suddenly become necessary because of gnome-common
> changes.  
> 
> If this patch works for you, I'm ok with it.  But don't we also need to ensure
> the m4/ directory exists by either:
> 
> 1) mkdir -p m4 in autogen.sh
> 2) Adding it in git with an empty .gitignore

Thanks. 

Just to make it easier for people using jhbuild who haven't come across this before if its in, really.

I did not know about 2. though! Cheers for the tip.