[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gettext] Endianness of .mo files
From: |
Daiki Ueno |
Subject: |
Re: [bug-gettext] Endianness of .mo files |
Date: |
Fri, 16 May 2014 15:58:22 +0900 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
Hi,
Santiago Vila <address@hidden> writes:
> There is a long discussion about .mo file endianness in this Debian
> bug report:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671257
>
> As a result, I applied the attached patch to the Debian package, which
> makes our work a lot easier, specially for multiarch.
After reading the discussion, I was left with a question.
When the GNU gettext infrastructure is used, upstream tarballs include
*.gmo files, which could have been generated in a different byte-order.
Does the recent Debian build system forcibly regenerate them on package
building?
> I wonder if it would be possible to have some sort of option which I
> can pass to ./configure to achieve this behaviour so that modifying
> msgfmt.c directly was not needed.
Yes, it could. But I doubt if it really helps multiarch packaging.
Perhaps it might be easier to run a small script that converts
byte-order of *.mo files after the "make install" phase.
Regards,
--
Daiki Ueno