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 128840 - cvs missed: po/Makefile.in
cvs missed: po/Makefile.in
Status: VERIFIED FIXED
Product: conglomerate
Classification: Other
Component: general
CVS
Other All
: Normal normal
: ---
Assigned To: conglomerate list
conglomerate list
Depends on:
Blocks:
 
 
Reported: 2003-12-08 20:55 UTC by Oleg Paraschenko
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Oleg Paraschenko 2003-12-08 20:55:21 UTC
In root folder, file "configure.in" has a reference to "po/Makefile.in":

----- <configure.in>
...
dnl --- Output ---

AC_OUTPUT(Makefile 
	  conglomerate.spec
          po/Makefile.in
...
----- </configure.in>

But there are no "po/Makefile.in" in CVS:

$ cat CVS/Repository 
conglomerate/po
$ cvs status Makefile.in
cvs status: nothing known about Makefile.in
===================================================================
File: no file Makefile.in               Status: Unknown

   Working revision:    No entry for Makefile.in
   Repository revision: No revision control file
Comment 1 Geert Stappers 2003-12-08 21:28:15 UTC
All files referenced in configure.in AC_OUTPUT(),
including po/Makefile.in, are generated.
It doesn't make sense to put them in CVS.

Feel free to re-open this bug report.
Comment 2 Oleg Paraschenko 2003-12-09 03:38:26 UTC
I'm sorry. I don't know autoconf stuff so good to be very sure in the
reason of problem. But commion sense suggests that some file is absent.

In order to generate file in AC_OUTPUT, you should have something as
source data for generation. For example: for file
"data/conglomerate.keys", there is file "data/conglomerate.keys.in" in
CVS; for file "debian/Makefile", there is file "debian/Makefile.am" in
CVS.

So my current suggestion is:

1) AC_OUTPUT should contain "po/Makefile", instead of "po/Makefile.in".
2) "po/Makefile.in" should be in CVS.

But I'm not sure, so I don't reopen issue.
Comment 3 Geert Stappers 2003-12-09 07:23:40 UTC
The po/ directory is a so what special directory,
it is generated/controlled by the internationalisation tools.
The file po/Makefile.in.in is the source for po/Makefile.in
Comment 4 Oleg Paraschenko 2003-12-09 07:40:37 UTC
> The file po/Makefile.in.in is the source for po/Makefile.in

Then I suggest to put "po/Makefile.in.in" into the CVS. Currently it
is missed:

http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&dir=conglomerate/po

or

$ cat CVS/Root 
:pserver:anonymous@anoncvs.gnome.org:/cvs/gnome
$ cat CVS/Repository 
conglomerate/po
$ cvs status Makefile.in.in 
cvs server: nothing known about Makefile.in.in
Comment 5 Geert Stappers 2003-12-09 08:23:19 UTC
Run the following test. (The dollar sign is used to indicate a prompt)

 $ cd /usr/src/conglomerate # or where ever you have the conglomerate tree
 $ cvs update -dP
 $ ./autogen.sh
 $ mv po po-backup
 $ cvs update -dP
 $ ./autogen.sh
 $ diff po-backup po


Comment 6 Oleg Paraschenko 2003-12-10 04:23:53 UTC
Finally I got "po/Makefile.in.in"

Problem was is that my system has problems on generating "./libtool".
I followed instructions in "doc/devel/CompileIssues" and used

autoreconf --install

for generation of configure script and make-files. But it is not a
task of "auroreconf" to create "po/Makefile.in.in". This file is
created by:

gettextize -f


I suggest you to update "doc/devel/CompileIssues": add a note about
possible problem with "po/Makefile.in.in" and about solution.


Thanks you for support!
Comment 7 Geert Stappers 2003-12-11 08:51:09 UTC
--- doc/devel/CompileIssues     5 Sep 2003 10:28:03 -0000       1.2
+++ doc/devel/CompileIssues     11 Dec 2003 08:46:44 -0000
@@ -26,7 +26,9 @@
 with the original "./autogen.sh". One solution is to run
 "libtoolize --automake". An other is one to run "autoreconf --install"
  
+When you mis po/Makefile.in.in then run "gettextize -f".
  
 Improvement to this is document is appreciated,
 especially because that the problems don't occure on all systems
  
+Please report the issues that you encounter!
Comment 8 Geert Stappers 2003-12-11 08:54:38 UTC
If you had an other text in mind, let us known.
Comment 9 Oleg Paraschenko 2003-12-11 12:10:24 UTC
Thanks, closing.


But instead

> When you mis po...

I prefer

> If you miss po...

But I don't know English and not sure.