This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: gmo files in binutils snapshot


Hi,

An angry mail was seen on the bug-gnu-utils list by someone who
apparently took a CVS snapshot of binutils, attempted to compile it on
a HP-UX machine which didn't have the gettext utilities installed, and
failed, with a scenario like this.

creating libbfd.la
(cd .libs && rm -f libbfd.la && ln -s ../libbfd.la libbfd.la)
        libtooldir=`/bin/sh ./libtool --config | sed -n -e 's/^objdir=//p'`; \
        if [ -f $libtooldir/libbfd.a ]; then \
          cp $libtooldir/libbfd.a libbfd.tmp; \
          ranlib libbfd.tmp; \
          /bin/sh ./../move-if-change libbfd.tmp libbfd.a; \
        else true; fi
        touch stamp-lib
        make  all-recursive
Making all in po
        file=./`echo fr | sed 's,.*/,,'`.gmo \
          && rm -f $file && PATH=../src:$PATH msgfmt -o $file fr.po
sh[2]: msgfmt:  not found.
*** Error exit code 127

The GNU gettext autoconf macros and po/Makefile.in.in rules are made
for a situation where the .gmo files (one for each .po file) are
present in the distribution. The purpose of this is that users can get
i18n support without needing to install extra tools. (Just like users
don't need autoconf and automake in order to compile a package that
uses Makefile.am's.)

In some projects it is inconvenient to add the .gmo's to the CVS tree,
because then they have to be regenerated every now and then, and
binary files under CVS control that change frequently occupy some
disproportionate disk space in the CVS repository. Such projects
therefore usually add the following lines to the produce-a-snapshot
script:

   for f in `find . -name '*.po' -type f -print`; do
     msgfmt -o `echo $f | sed -e 's/\.po$/.gmo/'` $f
   done

May I suggest that the binutils snapshots (and releases of course as
well) adopt such an approach, in order not to frustrate newbies?

                Bruno
                GNU gettext maintainer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]