Bug#190964: gcc-3.2: No .mo files included in the package?

[Matthias Klose <doko@cs.tu-berlin.de>]

Ole Laursen writes:
> Matthias Klose <doko@cs.tu-berlin.de> writes:
> 
> > > Some people have spent quite a lot of time translating GCC messages
> > > into other languages (yeah, I happen to be one of them). But these
> > > translation .mo files don't seem to be included in any of the Debian
> > > packages.
> > 
> > they are, but now for gcc-3.3, because the files clash with
> > gcc-3.2. I'm happy to include a patch to look for gcc-X.Y.mo instead
> > of gcc.mo.
> 
> Ah, see. Didn't understand the issue, either, since I recall them
> being distributed before. But I had seen weirder things with other
> packages.
> 
> Well, I've downloaded the GCC tarball and looked at it. AFAICS,
> renaming the package specified in gcc/configure.in to include the
> version number should do the trick (GNOME programs do the same to
> handle the GNOME 1.x -> GNOME 2.x transition). The attached patch does
> that.
> 
> --- gcc/configure.in	2003-02-04 01:17:41.000000000 +0100
> +++ gcc/new-configure.in	2003-04-30 00:31:18.000000000 +0200
> @@ -942,7 +942,7 @@
>  changequote([,])dnl
>  
>  # Internationalization
> -PACKAGE=gcc
> +PACKAGE=gcc-3.2
>  VERSION="$gcc_version"
>  AC_SUBST(PACKAGE)
>  AC_SUBST(VERSION)

close. adding the following patch seems to work:

diff -ur gcc-20030118/gcc/Makefile.in src/gcc/Makefile.in
--- gcc-20030118/gcc/Makefile.in        2003-01-09 19:30:05.000000000 +0100
+++ src/gcc/Makefile.in 2003-01-20 01:21:02.000000000 +0100
@@ -2164,6 +2164,7 @@
 intl.o: intl.c $(CONFIG_H) system.h intl.h Makefile
        $(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) \
          -DLOCALEDIR=\"$(localedir)\" \
+         -DPACKAGE=\"$(PACKAGE)\" \
          -c $(srcdir)/intl.c $(OUTPUT_OPTION)

--- src/gcc/intl.c~     2002-03-02 00:38:00.000000000 +0100
+++ src/gcc/intl.c      2003-04-28 13:13:22.000000000 +0200
@@ -39,8 +39,8 @@
   setlocale (LC_ALL, "");
 #endif

-  (void) bindtextdomain ("gcc", LOCALEDIR);
-  (void) textdomain ("gcc");
+  (void) bindtextdomain (PACKAGE, LOCALEDIR);
+  (void) textdomain (PACKAGE);
 }

 #endif


> > > I don't know if that is a problem with upstream not including them,
> > > but anyway the latest files are available here:
> > > 
> > >   http://www2.iro.umontreal.ca/~pinard/po/registry.cgi?domain=gcc
> > 
> > maybe you want to help upstream applying these patches? They are
> > currently sent to the gcc-patches list and have to be checked in by
> > hand.
> 
> Applying patches? Do you mean the .po files? How can I help with them?
> It is just a question of replacing the old ones. If I could help, I
> would love to. Apparently, the gcc-3.2.3 tarball contains the
> translation for 2.95, which is completely outdated. Sigh.

Search in the gcc mailing list at gcc.gnu.org. I think it's too late
for 3.2.x, but 3.3 and HEAD would be the right places for this work.
If I understand correctly, you would need to send .pot files to the
translation project from time to time, and checkin the .po files,
which are sent to gcc-patches.

	Matthias