Daniel E. Macks <dmacks <at> netspace.org> writes:

>> On Fri, Apr 16, 2010 at 03:49:57AM +0200, J-F Mertens wrote:
> > When instaling gdb, I get:
> > 
> > dpkg - warning, overriding problem because --force enabled:
> > trying to overwrite `/sw/share/locale/da/LC_MESSAGES/bfd.mo', which  
> > is also in package binutils
> > dpkg - warning, overriding problem because --force enabled:
> > trying to overwrite `/sw/share/locale/da/LC_MESSAGES/opcodes.mo',  
> > which is also in package binutils
> 
> If gettext catalogs are the collision, they can usually be renamed
> easily. A few libraries play that same game so (per Shlibs Policy)
> multiple versions can be installed without overwriting each other.
> 
> Exactly *how* depends on the source and build system, but generally
> the filename is the "domainname" passed to dgettext() or
> bindtextdomain(), and is also set in the makefile in po/ (or its
> templates and processors). Could have opcodes-gdb and
> opcodes-binutils, for example.

Trying to read the build-scheme in binutils (must be the same for gdb 
_ same src!)
it seems first that   s/@PACKAGE@/%N-&/  in {bfd,opcodes}/po/Make-in
might do what you suggest.
But then I read in bfd/sysdep.h

/* Note the use of dgetext() and PACKAGE here, rather than gettext().

   This is because the code in this directory is used to build a library which
   will be linked with code in other directories to form programs.  We want to
   maintain a seperate translation file for this directory however, rather
   than being forced to merge it with that of any program linked to libbfd.
   This is a library, so it cannot depend on the catalog currently loaded.

   In order to do this, we have to make sure that when we extract messages we
   use the OPCODES domain rather than the domain of the program that included
   the bfd library, (eg OBJDUMP).  Hence we use dgettext (PACKAGE, String)
   and define PACKAGE to be 'bfd'.  (See the code in configure).  */
#define _(String) dgettext (PACKAGE, String)

That type of game makes me afraid that I might have to change
PACKAGE about everywhere to become %N-PACKAGE
_ and have no idea what other sideffects this may have ..

Except if you have a better suggestion, I'm thinking of just using
update-alternatives (the .mo files must be identical..).

JF


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to