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 130469 - Doesn't build out of CVS
Doesn't build out of CVS
Status: RESOLVED DUPLICATE of bug 130280
Product: gnome-mime-data
Classification: Deprecated
Component: Default
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Mime Data Maintainers
GNOME Mime Data Maintainers
: 130537 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-01-03 21:15 UTC by Jon Kåre Hellan
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Attachments
jhbuild build log (22.74 KB, text/plain)
2004-01-03 23:01 UTC, Jon Kåre Hellan
Details
intltool-extract.in (10.35 KB, text/plain)
2004-01-04 01:59 UTC, Jon Kåre Hellan
Details

Description Jon Kåre Hellan 2004-01-03 21:15:22 UTC
gnome-mime-data doesn't build out of CVS.
cleaning out the old gnome-mime-data directory and doing 
jhbuild buildone gnome-mime-data results in

make[2]: *** No rule to make target `gnome-vfs.keys', needed by `all-am'.

tool versions:
autoconf: 2.58
automake: 1.4
intltool: 0.28 (actually CVS)
Comment 1 Bastien Nocera 2004-01-03 22:44:29 UTC
Works fine here. Please include the whole output of ./autogen.sh
followed by make, and the resulting Makefile.
Also bear in mind that GNOME 2.4 and above require newer versions of
automake (1.7 being a reasonable version).
Comment 2 Jon Kåre Hellan 2004-01-03 23:01:08 UTC
Created attachment 22883 [details]
jhbuild build log
Comment 3 Jon Kåre Hellan 2004-01-03 23:07:47 UTC
Re automake versions: I have automake-1.4 p6, automake-1.6 and
automake-1.7. However, plain automake is 1.4 p6 on Debian sid. 
autogen.sh checked if automake was >= 1.4 and was content with that.

Shouldn't you make the dependency on 1.7 explicit? Or don't we support
systems where plain automake is 1.4? If so I can set up a symlink.
Comment 4 Bastien Nocera 2004-01-04 01:15:56 UTC
It looks like you've got an old version of gnome-common or there is
something wrong with your installation:
./config.status: line 1104: /intltool-extract.in: No such file or
directory
mv: cannot stat `intltool-extract.out': No such file or directory
chmod: failed to get attributes of `intltool-extract': No such file or
directory
chmod: failed to get attributes of `intltool-extract': No such file or
directory
etc.

What is intltool-extract.in?
Comment 5 Jon Kåre Hellan 2004-01-04 01:59:49 UTC
Created attachment 22888 [details]
intltool-extract.in
Comment 6 Jon Kåre Hellan 2004-01-04 02:02:33 UTC
I cleaned the gnome tree yesterday, both the installation tree and the
source tree. So  unless versions outside the build prefix interfere,
this shouldn't be due to old gnome-common
Comment 7 Bastien Nocera 2004-01-05 07:53:35 UTC
*** Bug 130537 has been marked as a duplicate of this bug. ***
Comment 8 Jon Kåre Hellan 2004-01-05 09:02:15 UTC
I now have a strong suspicion that CVS intltool is at fault.
gnome-mime-data just has the bad luck to be the first module affected
in the build sequence. I've seen similar behaviour - .foo files not built 
from foo.in files, when building yelp and gnumeric.

It could still be wrong automake version or a bug in gnome-common, I
guess. What seems to be happening is that the rule to generate .foo
from .foo.in isn't included in the makefile, and I'm not sure who is
responsible for this.

If it were up to me, I'd reassign this to intltool and see what happens.
Comment 9 Bastien Nocera 2004-01-05 13:07:45 UTC

*** This bug has been marked as a duplicate of 130280 ***
Comment 10 Thomas Vander Stichele 2004-01-06 08:24:38 UTC
Jon Kare Hellan: please jhbuild buildone intltool, then retry and let
us know.
Comment 11 Jon Kåre Hellan 2004-01-06 10:19:06 UTC
I did rebuild intltool, and things now work for me.